-
Notifications
You must be signed in to change notification settings - Fork 44
feat: Enhanced withCallState to accept mutliple collection configuration
#148
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
|
This requires additional changes and need to fix the typescript errors |
c74218f to
86baae1
Compare
86baae1 to
8b89c58
Compare
…ns with an array
…ation with backward compatibility
…ation with backward compatibility
…ation backward compatibility
…ns with an array
|
@rainerhahnekamp did you get time to review this? |
rainerhahnekamp
left a comment
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.
Well done and sorry for the late reply. What I'm currently asking myself, if we could use collections instead of collection to support the array of strings?
Would that be a big issue?
Well initially I did exactly that but then it would be a breaking change |
In which regard? To me, it would be an additional property. It would be breaking if |
fix(ngrx-toolkit): accept collection to collections in withCallState
fix unit test
|
@rainerhahnekamp I have made the changes one more thing is we no longer need getCallStateKeys method here let me know if you want me to do that change or we should leave it as it is Thanks |
rainerhahnekamp
left a comment
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.
LGTM
|
Thanks @abhijit-chikane |
feat: Enhanced
withCallStateto accept mutliple collection configurationFor #147
I have not tested it but happy to help if in case it didn't work as expected
thanks