Fixes #371 - throttle using strategy input should cache results #372
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 updates the Switcher Client SDK to version 2.5.1 and fixes throttle feature when using Strategy inputs. The issue was that the mapper wasn't assigning the entries (Strategy inputs) to the copied response object, which caused the cache to have invalid entries.
Refactoring and code maintenance:
KEY,SHOW_REASON,BYPASS_METRIC) fromSwitcherRequestto theClientWSinterface, and updated all references to use the new location. [1] [2] [3]switchertoswitcherRequestin service classes and test files. [1] [2] [3]Functional improvements:
Mapper.mapFrommethod to correctly set theentryfield inSwitcherResultby passing theSwitcherRequestobject, ensuring accurate mapping between requests and responses.SwitcherRequestby referencing the correctentryfield instead of using a getter, improving cache hit accuracy.