feat: changed flush to clean execution history too (#379) #380
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 improvements to the handling of execution history in the SwitcherBuilder class and refactors test code to use a constant for the default environment, improving maintainability and consistency. The most significant change is the centralization of the historyExecution map in SwitcherBuilder, along with updates to test setup and usage patterns.
Environment configuration improvements
"default"environment string with theDEFAULT_ENVconstant fromcom.switcherapi.client.remote.Constantsacross all test classes, improving maintainability and reducing duplication. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]SwitcherBuilder and execution history refactor
historyExecutionmap fromSwitcherRequestto the baseSwitcherBuilderclass, centralizing execution history management for all builder subclasses. [1] [2] [3]flush()method inSwitcherBuildernow clears both entries and execution history, improving the reset logic for builder state.Test and usage updates
SwitcherThrottleTestto useSwitcherBaseand the new environment configuration, and removed unnecessary test ordering and initialization calls for clarity and consistency. [1] [2] [3] [4] [5]