-
Notifications
You must be signed in to change notification settings - Fork 11.8k
chore: Internally operate Minimongo collections over Zustand stores (as transition for stores-only) #35470
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
Conversation
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
|
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #35470 +/- ##
===========================================
- Coverage 64.97% 64.51% -0.46%
===========================================
Files 3112 3123 +11
Lines 93795 97840 +4045
Branches 17810 18513 +703
===========================================
+ Hits 60944 63123 +2179
- Misses 30065 31893 +1828
- Partials 2786 2824 +38
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
affd24f
to
aad0285
Compare
3391c85
to
d0f4a7b
Compare
4143ece
to
6b60ebe
Compare
Proposed changes (including videos or screenshots)
It prepares for a migration from Meteor-dependent Minimongo collections to Zustand stores by making the said collections store their data into the stores.
Issue(s)
ARCH-1483
Steps to test or reproduce
Further comments
Instead of writing statements like
the developer is encouraged to use the Zustand store as a hook
Although not as ergonomic as the Minimongo API, writing selector functions is more portable and performant than Mongo-like query objects.