- Dec 22, 2023
-
-
Joel Jeremy Marquez authored
* Enable prefer-const project-wide * Release notes * Fix remaining lint errors
-
Matiss Janis Aboltins authored
-
- Dec 18, 2023
-
-
DJ Mountney authored
-
- Dec 09, 2023
-
-
Joel Jeremy Marquez authored
* Another round of prefer-const rule updates * Release notes * Fix test error * Fix sync.ts
-
- Dec 05, 2023
-
-
Joel Jeremy Marquez authored
* ESLint prefer-const components folder part 2 * Release notes
-
Joel Jeremy Marquez authored
* ESLint prefer-const components folder part 1 * Release notes
-
Matiss Janis Aboltins authored
-
- Nov 22, 2023
-
-
Matiss Janis Aboltins authored -
Joel Jeremy Marquez authored
* Part 2 of eslint prefer-const * Release notes * Update
-
Joel Jeremy Marquez authored
-
- Nov 21, 2023
-
-
Matiss Janis Aboltins authored
-
- Nov 11, 2023
-
-
Matiss Janis Aboltins authored
-
- Sep 16, 2023
-
-
Neil authored
-
- Sep 13, 2023
-
-
Neil authored
-
- Sep 11, 2023
-
-
Neil authored
-
- Sep 09, 2023
-
-
Neil authored
-
Matiss Janis Aboltins authored
-
- Sep 05, 2023
-
-
Joel Jeremy Marquez authored
* Break apart budget/misc.js * Release notes * Rename release notes * UI bolder "No server" text
-
- Aug 19, 2023
-
-
Matiss Janis Aboltins authored
-
- Aug 16, 2023
-
-
Matiss Janis Aboltins authored
-
- Aug 13, 2023
-
-
- Aug 09, 2023
-
-
Neil authored
-
- Aug 07, 2023
-
-
Neil authored
This is to prevent any further color changes added to PRs. This will help prevent the darkTheme getting any addition work loaded onto it.
-
- Jul 18, 2023
-
-
Jed Fox authored
-
- Jul 17, 2023
-
-
Jed Fox authored
-
- Jun 30, 2023
-
-
Shazib Hussain authored
-
- Jun 28, 2023
-
-
Jed Fox authored
I noticed that: - The web and electron versions of our `uuid` module both looked exactly the same… - …and deferred to the `uuid` package… - …and the async version just called the sync API. So now we will just use the `uuid` package directly everywhere.
-
- Jun 27, 2023
-
-
Jed Fox authored
This cleans up all of the usage of `<a>` in the codebase. Now all external links get the appropriate attributes added.
-
- Jun 26, 2023
-
-
Jed Fox authored
This significantly speeds up `yarn lint` for me. It also ensures we’re listing all source files in the project, including the `.eslintrc` files and any other files that may be present.
-
- Jun 24, 2023
-
-
Shazib Hussain authored
- New linter rules are now added - Perhaps the `createPayee` method i've tagged with a disable should be deleted. - I have ignored unused methods in Plaid/Mobile as this stuff is still WIP/experimental?
-
- Jun 09, 2023
-
-
Jed Fox authored
Bundle sizes are unchanged but now we no longer pull in the Electron-specific FS code on the web version
-
- May 29, 2023
-
-
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`)
-
- May 28, 2023
-
-
Jed Fox authored
-
- May 09, 2023
-
-
Alberto Gasparin authored
-
Jed Fox authored
Multi-line `if`/`for` statements in JS can be confusing since there aren’t braces to indicate which code is enclosed in the statement. I set the configuration to `multi-line` to enforce usage of braces for multi-line statement bodies, but still allow things like `if (foo) return;`. I additionally added the `consistent` option to require braces for all elements of an if/else chain if one element has it. As you can see, this set of options pretty closely matches the existing code style. I was going to comment in #1008 about this stylistic change but realized that it’s (IMO) a little impolite to ask for code style changes unless they can be automatically enforced. Note that `if (foo) { \n return; \n }` is still valid and won’t be collapsed. I tried to automatically collapse all such cases but it was a lot of files and I didn’t want to pick out the useful from the useless differences.
-
- Apr 30, 2023
-
-
Trevor Farlow authored
Switch to TS version of `no-unused-vars` rule.
-
- Apr 21, 2023
-
-
Jed Fox authored
I got some feedback in the discord that this behavior was disruptive when zooming in. - I’ve reduced the breakpoint so hopefully the disruption of the transition is matched by a significant improvement in available space now. - Also the 2 places in the app that use window width (including here) now check for the width of the `<html>` tag, not the width of the viewport (those 2 values can be different when doing a pinch-zoom, causing undesirable layout shifts.) - Most of the logic has been rewritten to improve the transitions Mobile & desktop experience https://user-images.githubusercontent.com/25517624/233653721-b13c5e22-ae11-4bdf-a494-a6916556d05e.mov https://user-images.githubusercontent.com/25517624/233654784-b6cc1006-44ea-4066-be7a-8d0dd786fb5b.mov (I’d like tapping on something to close the sidebar on mobile, but that can be approached in a future PR)
-
- Apr 12, 2023
-
-
Alberto Gasparin authored
Another batch of files from `loot-core` migrated to TS (loose mode)
-
- Apr 03, 2023
-
-
Alberto Gasparin authored
Part 1 of the conversion. Mostly renaming js to ts and making sure things make still sense. Added also handy TS ESLint rules. In order to support the various .web/.electron/... I ended up adopting `index.d.ts` as pattern to share type definition. Let me know if that makes sense for you too. Right now the function type definition is duplicated, but the solution will be importing from `index.d.ts` and using `const fn: FnDef = () => ...` that way we can keep all variants in sync from a single type file. Such rewrite however is better done in another PR otherwise we risk confusing git and loosing history (rename + too many changes). Another thing that might do in the next PR is convert all files to ESModules, as things get confusing between CJS exports, ESM default/named and TS adds extra complains.
-
- Mar 21, 2023
-
-
Jed Fox authored
-
