feat: add strictStateCheck option to disable state warnings#282
Open
sizeak wants to merge 1 commit intojorisre:mainfrom
Open
feat: add strictStateCheck option to disable state warnings#282sizeak wants to merge 1 commit intojorisre:mainfrom
sizeak wants to merge 1 commit intojorisre:mainfrom
Conversation
Add a new `strictStateCheck` option (default: true) that controls whether warnings are logged when `request`/`release` are called in invalid states. Setting it to `false` makes these methods fully idempotent with no console output, while still preventing duplicate API calls. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
|
@sizeak is attempting to deploy a commit to the Joris' projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi,
We're using this library but we'd like to be able to disable the warning logs when multiple calls of
request/releaseare triggered in a row. Would you be happy to include this functionality? Happy to make changes if you're not a fan of how I've implemented it.Thanks for the library!
Changes
Add a new
strictStateCheckoption (default: true) that controls whether warnings are logged whenrequest/releaseare called in invalid states. Setting it tofalsemakes these methods fully idempotent with no console output, while still preventing duplicate API calls.