Skip to content
Snippets Groups Projects
  1. Jun 17, 2023
  2. Jun 16, 2023
  3. Jun 15, 2023
  4. Jun 14, 2023
  5. Jun 13, 2023
  6. Jun 11, 2023
    • Jed Fox's avatar
      Fix sync-related errors that show up in the console when not using a server (#984) · 0e2b317e
      Jed Fox authored
      Previously, the frontend would attempt to make real requests to
      `https://not-configured/`, which of course failed. I’ve changed the
      internal structure to have the lack of a server expressed as a `null`
      server. A new `did-bootstrap` browser-level setting has been added to
      track if the user clicked “Don’t use a server.”
      
      Finally, I updated the auth logic for methods that call out to the
      server to make them consistent and use the early return style which
      reduces indentation.
      0e2b317e
    • Jed Fox's avatar
      Partition GitHub Actions cache based on Node version (#1118) · 15bc3c45
      Jed Fox authored
      This should fix the test failures on `master` — currently tests are
      failing because the cache was created with an old version of Node.
      15bc3c45
    • youngcw's avatar
      Goals: Check template action (#1108) · ded6ee8a
      youngcw authored
      This adds an option to the month drop down to check all the template
      lines. If there are errors the offending line is shown with its
      category.
      
      I also modified the wording on the regular template return to be more
      accurate. Fixes #1100
      ded6ee8a
  7. Jun 10, 2023
    • Jed Fox's avatar
      Update recommended version to Node.js 18 (#1117) · c1af40ff
      Jed Fox authored
      After #1115, new Node.js versions will be able to be used for
      development of the frontend. This PR changes the recommended Node.js
      version to 18 (the current LTS version). I have also tested with 16 and
      20 and it works.
      
      I also took the opportunity to:
      
      - move the build script that was at the project root to the `bin/`
      folder
      - update the `browserslist` to target Electron 24 (which is the version
      we currently build against). This results in a slightly smaller bundle
      due to no longer having to transpile optional chaining.
      c1af40ff
    • Jed Fox's avatar
      Update loot-core to webpack 5 (#1115) · f06edd72
      Jed Fox authored
      ~based on #1114~
      
      This brings its build process up to date with the rest of the project.
      We can now use Node 20 to build successfully.
      
      Closes #918
      f06edd72
  8. Jun 09, 2023
  9. Jun 08, 2023
    • Davis Silverman's avatar
      Remove 'new' OFX parser as it is too buggy (#1111) · 87d269ba
      Davis Silverman authored
      Draft because it is untested, maybe tonight I will test it! Just wanted
      to get some code out cause i had a spare 5 minutes.
      
      The new parser isn't immediately good enough to replace the old parser,
      and I sadly lost the time to contribute more! Sorry! If someone else
      wants to take maintenance burden of this code, we can not merge this.
      Otherwise, it should go the way of the Dodo it seems.
      
      Thanks!
      
      Closes #1044
      87d269ba
    • Jed Fox's avatar
      Fix migration ID for “remove account type” migration (#1109) · 6e6d7656
      Jed Fox authored
      Good catch @Jackenmen in
      https://github.com/actualbudget/actual/pull/948#issuecomment-1580501909
      — I’ve also added a CI check to ensure bad migrations aren’t introduced
      in the future.
      
      I think if you have a budget that has managed to have this migration
      applied successfully, you’ll need to manually patch
      `getAppliedMigrations` in
      `packages/loot-core/src/server/migrate/migrations.ts` and inject a query
      to remove the old migration ID and insert the new one.
      6e6d7656
  10. Jun 06, 2023
    • Jed Fox's avatar
      Remove account types (#948) · a25327d3
      Jed Fox authored
      Closes #944, closes #532. ~WIP because something is causing the test
      budget to fail to create because it’s using INSERT instead of UPDATE sql
      queries. (Or not? I have no idea)~
      a25327d3
    • youngcw's avatar
      Goals: Remainder option (#1101) · ed285e9a
      youngcw authored
      Added the option to add a remainder goal template. This will use the
      remaining available funds and dump them into the respective category.
      There is optional weighting. The remainder templates will be forced to
      the lowest priority as to run after all other templates.
      
      Usage: `#template remainder <weight>` Add the template line to any
      categories you want to catch any remaining funds such as savings. The
      amount added to the category will equal
      `remaining_budget/total_of_weights*weight`. The default weight is 1.
      ed285e9a
  11. Jun 05, 2023
  12. Jun 04, 2023
  13. Jun 03, 2023
  14. Jun 02, 2023
  15. Jun 01, 2023
  16. May 30, 2023
    • shall0pass's avatar
      Goals: Schedule include spent value in calculation (#1049) · bb1a4747
      shall0pass authored
      
      This adds back the functionality, which was inadvertantly removed, that
      includes the already spent column in the calculation when the template
      is run.
      
      Some transactions may be posted to the account prior to running the
      templates and would result incorrect budgeted amounts.
      
      ---------
      
      Co-authored-by: default avatarJed Fox <git@jedfox.com>
      bb1a4747
    • shall0pass's avatar
      End of month cleanup script (#1016) · d6408599
      shall0pass authored
      ~This is really just a proof of concept. I have no delusions that this
      might get included. I'm sure others might have a much cleaner
      implementation.~
      I'm now delusional.
      
      Resolves https://github.com/actualbudget/actual/issues/508
      
      Taking @youngcw 's advice, I changed the keyword to #cleanup for the end
      of month script to keep it separated.
      
      This screen video shows two categories that are sources of funds. At the
      end of the month, any excess in these funds can be redistributed to your
      highest priorities. Three categories are set as sinks, or recipients, of
      excess funds.
      
      #cleanup source   -> Move 'extra' funds to To Budget
      #cleanup sink -> Fund category with To Budget funds, default weight = 1
      #cleanup sink 2       -> Fund category with To Budget funds, weight = 2
      
      Steps of the script:
      1. Return funds from any category marked 'source'
      2. Fund overspent categories fully if negative carryover is not allowed.
      3. Fund each 'sink' category by the desired weight.
      
      I run through the script twice. Once to show that if there is a debt
      category that has a rolling negative balance, it will skip funding that
      category first and once to show how if a rolling negative balance isn't
      allowed, it will fund it before applying the weighted remainder. The
      example shown uses weights of 60, 20, and 20; therefore, the Debt
      category will receive 60% of the To Budget funds while General and Bills
      receive 20% each. The weights could have been changed to 6, 2, and 2 or
      3 for the Debt category with no additional value for General and Bills
      to achieve the same result.
      
      
      ![cleanup_button](https://github.com/actualbudget/actual/assets/20625555/56ae2b29-9be6-4e85-b532-1b05cff7c4c7)
      d6408599
  17. May 29, 2023
    • Jed Fox's avatar
      More import-related ESLint rules (#1070) · e660e1e7
      Jed Fox authored
      - Enforce that imports from the same package are merged into a single
      import
      - In `loot-core`, require that imports of other `loot-core` files use a
      relative import (like the vast majority of such imports) rather than
      specifiers starting with `loot-core/` (probably a result of moving files
      out of other packages into `loot-core`)
      e660e1e7
Loading