Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sync follow up issues #278

Merged
merged 2 commits into from
Dec 8, 2024
Merged

sync follow up issues #278

merged 2 commits into from
Dec 8, 2024

Conversation

cloverich
Copy link
Owner

@cloverich cloverich commented Dec 8, 2024

  • read documents directly from disk, rather than db, to sidestep desync issues

also run sync on startup; add sync throttle; refactor types

  • run sync on startup (naive way to avoid desync)
  • add basic throttling mechanism and stats to sync (view new sync table)
  • refactor: move types out of preload/documents, to avoid accidental node type inclusion in prod (breaks build)
  • refactor: use useJournals insstead of useContext(JournalStoreContext) in several places

Closes #252

- read documents directly from disk, rather than db, to sidestep desync issues
- run sync on startup (naive way to avoid desync)
- add basic throttling mechanism and stats to sync (view new sync table)
- refactor: move types out of preload/documents, to avoid accidental node type inclusion in prod (breaks build)
- refactor: use useJournals insstead of useContext(JournalStoreContext) in several places
@cloverich cloverich merged commit 344bf13 into master Dec 8, 2024
2 checks passed
@cloverich cloverich deleted the sync_followup branch December 8, 2024 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Sync follow-up issues
1 participant