-
Notifications
You must be signed in to change notification settings - Fork 3
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
New withCalls enabled prop #134
Labels
Comments
gabrielguerrero
pushed a commit
that referenced
this issue
Sep 17, 2024
New enabled function in withCalls config allows to skip the call under certain user defined conditions like when params are null, or result was already cached fix #134
gabrielguerrero
pushed a commit
that referenced
this issue
Sep 18, 2024
New enabled function in withCalls config allows to skip the call under certain user defined conditions like when params are null, or result was already cached fix #134
gabrielguerrero
pushed a commit
that referenced
this issue
Sep 18, 2024
New skipWhen function in withCalls config allows to skip the call under certain user defined conditions like when params are null, or result was already cached fix #134
🎉 This issue has been resolved in version 18.2.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is to add a new prop to the typedCallConfig of withCalls called enabled, which will receive a function that receives the params and can return a boolean or Observable or Promise, if true, the call is executed as usual if false the call is ignored and no state changes will be made, useful for cases where the call should be skipped if the param is null, or if the call for the give param was already cached.
Example:
The text was updated successfully, but these errors were encountered: