feat: added flushExecutions to clear cached results #100
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.



This pull request introduces a new feature to flush cached executions for a specific switcher, updates relevant documentation, and includes minor improvements and tests to support this functionality. The main focus is to allow users to clear throttled or cached results for a given switcher key, improving control over feature flag evaluations.
New Feature: Flush Cached Executions
flushExecutions()method to theSwitcherclass that clears cached executions for the current switcher key by calling the newExecutionLogger.clearByKey()utility. [1] [2]flushExecutions()method in theREADME.mdwith usage examples for users.flushExecutions()properly clears cached executions for a specific switcher key.Minor Improvements
isItOn()method inSwitcherto always return a resolved promise when called asynchronously, ensuring consistent async behavior.executemethod parameter to indicate it can accept a switcher key or aforceAsyncboolean.tests/playground/index.tsto accurately reflect requirements and usage of async calls.