-
Notifications
You must be signed in to change notification settings - Fork 219
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
feat(store): M.splitArray and M.splitRecord #6597
Conversation
9f60267
to
5fedea2
Compare
cd1cca9
to
6b8b56c
Compare
1371826
to
6405c35
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just to provide the new feature. Because it is compat, this PR does not itself refactor the usage to use the feature.
This PR does change about a dozen test files outside store
package so it looks like there are some changes here to adopt the feature. Maybe in defendSyncArgs
using the new M.splitArray
. I would have expected that change to be saved for #6431 .
That's not a blocker but I am requesting the documentation updates on MatchHelper
6405c35
to
47b5c90
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see request was satisfied by a "fix" commit. That shouldn't go into master so when merging please use "squash". Or squash locally when you fix the lint error.
47b5c90
to
5c2885d
Compare
5c2885d
to
6344cff
Compare
As suggested at #6431 (review) , this PR is extracted from #6431 just to provide the new feature. Because it is compat, this PR does not itself refactor the usage to use the feature.
So that we only bother to change most of these error messages once, this PR also borrows some code from #6432 for generating somewhat better errors.