Skip to content
Snippets Groups Projects
  1. Dec 27, 2023
  2. Dec 22, 2023
  3. Dec 19, 2023
  4. Dec 18, 2023
  5. Dec 15, 2023
  6. Dec 14, 2023
    • Julian Dominguez-Schatz's avatar
      Add schedule end date/count field (#1899) · c09a85f3
      Julian Dominguez-Schatz authored
      * Add "end" field with date/count options
      
      * Use "end" field to generate schedule
      
      * Show "end" field in recurring description
      
      * Disable weekend before/after picker when not enabled
      
      * Add release notes
      
      * Fix failing typechecks
      
      * Add some description tests
      
      * PR feedback
      
      * 'Features', not 'Feature'
      
      * Fix goal templates infinite loop
      
      * Empty commit to bump ci
      
      * Fix bug where schedule templates in the past would apply incorrectly
      
      For example, if you had a schedule which started in November 2023 for
      1.00, and you applied the schedule in October 2023, then you would end
      up with a value of 0.50 applied in October.
      
      * Fix handling of schedules with an end date
      
      This commit also includes a refactor of the skip-weekend logic: rather
      than referring only to dates with skipped weekends (which requires
      checking whether the "next date" request worked correctly), we track a
      "base date" which is the previous value of the schedule according to the
      rrule, excluding any weekend-skipping. This lets us use `addDays(baseDate, 1)`
      to get the next occurrence, regardless of the weekend behaviour.
      
      Doing things this way ensures that the loop will always make progress.
      
      * Only compute skipped weekend if weekend skips were requested
      
      * Fix typo in iterate-schedule-occurrences code
      
      We should be using `nextBaseDate` to derive the next base date, not
      `nextDate`; this is because we want the base date to be guaranteed to
      make progress in each loop iteration, so we can finish in at most 30
      iterations without duplicate base dates.
      
      * Use const
      
      * Revert const -> let for one mutable variable
      Unverified
      c09a85f3
  7. Dec 13, 2023
  8. Dec 09, 2023
  9. Dec 06, 2023
    • Neil's avatar
      Custom Reports optimization (#1988) · 2741422c
      Neil authored
      * Range fix and payee fix
      
      * bug fixes and UI tweaks
      
      * range options, hover UI
      
      * Select - UnSelect All Buttons
      
      * fix hidden group bug
      
      * YAxis PrivacyFilter
      
      * notes
      
      * more privacyFilter graphs
      
      * overflowY fix
      
      * Loading Indicator
      
      * Fix Filter button hover
      
      * data revamp
      
      * review fixes
      
      * LoadingIndicator fixes
      
      * remove a loop
      
      * filterbuttontype
      
      * lint fixes
      
      * review fixes
      
      * filtersbutton
      
      * updates
      
      * Split out functions to separate files
      
      * uncategorized optimization
      
      * rename ambiguous variables
      
      * notes
      
      * remove indexStack
      
      * renaming variables
      
      * Improve scrolling of tableGraph
      
      * revert renaming variables
      
      * code fixes
      
      * lint fixes
      
      * review fixes
      
      * fix
      
      * review fixes
      
      * variable name changes
      
      * const eslint fixes
      
      * remove indexStack
      Unverified
      2741422c
    • Matiss Janis Aboltins's avatar
  10. Dec 05, 2023
    • Kyle Mckay's avatar
      Fix failure to create category with deleted name (#2002) · c4ff099f
      Kyle Mckay authored
      * Fix failure to create category with deleted name
      
      I'm not 100% familiar with the design of the data model so may have
      misinterpreted what's going on here, but how I read this:
      
      - The tombstone flag is used to soft delete categories.
      - When creating a new category, duplicate names within a group are
        prevented.
      - When checking for duplicate names, the tombstone flag was unchecked
        which meant deleted categories were falsely blocking creation.
      
      I had a look at category deleteion logic to verify that simply including
      the tombstone flag in this check is sane and see that there's a category
      mapping being maintained to redirect one category to another on
      deletion. So from what I can tell the correct behaviour here is to allow
      a new category with the previously deleted name, rather than to revive
      the old category (to preserve that old mapping lineage).
      
      * Add release note
      
      * Add regression test
      Unverified
      c4ff099f
  11. Dec 01, 2023
  12. Nov 30, 2023
  13. Nov 28, 2023
  14. Nov 26, 2023
  15. Nov 23, 2023
  16. Nov 22, 2023
  17. Nov 20, 2023
  18. Nov 17, 2023
  19. Nov 15, 2023
  20. Nov 11, 2023
  21. Nov 08, 2023
  22. Nov 05, 2023
  23. Nov 04, 2023
  24. Oct 30, 2023
  25. Oct 22, 2023
  26. Oct 10, 2023
  27. Oct 06, 2023
  28. Sep 26, 2023
  29. Sep 24, 2023
Loading