There was an error fetching the commit references. Please try again later.
Fix sync-related errors that show up in the console when not using a server (#984)
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.
Showing
- packages/desktop-client/src/components/ServerContext.js 2 additions, 10 deletionspackages/desktop-client/src/components/ServerContext.js
- packages/desktop-client/src/components/manager/subscribe/common.tsx 2 additions, 1 deletion...esktop-client/src/components/manager/subscribe/common.tsx
- packages/desktop-client/src/hooks/useFeatureFlag.ts 1 addition, 0 deletionspackages/desktop-client/src/hooks/useFeatureFlag.ts
- packages/loot-core/src/server/accounts/sync.ts 48 additions, 49 deletionspackages/loot-core/src/server/accounts/sync.ts
- packages/loot-core/src/server/cloud-storage.ts 1 addition, 1 deletionpackages/loot-core/src/server/cloud-storage.ts
- packages/loot-core/src/server/main.ts 146 additions, 126 deletionspackages/loot-core/src/server/main.ts
- packages/loot-core/src/types/main-handlers.d.ts 2 additions, 2 deletionspackages/loot-core/src/types/main-handlers.d.ts
- upcoming-release-notes/984.md 6 additions, 0 deletionsupcoming-release-notes/984.md
Loading
Please register or sign in to comment