feat: added keepExecutions state to improve resource allocation

[petruki]

This pull request refactors the way switcher executions are tracked and managed, replacing the previous "history" terminology and logic with a clearer "executions" concept. It introduces new methods for managing execution records, improves API clarity, and updates documentation and tests to reflect these changes. This change should also considerably improve performance for local and remote if there is no need to keep the executions results.

Execution management improvements:

• Replaced the historyExecution map in SwitcherRequest with executionsMap, and updated all related logic and method names to use "executions" instead of "history". This includes renaming updateHistoryExecution to updateExecutions, and updating how results are stored and retrieved. [1] [2] [3] [4]
• Added flushExecutions() to the Switcher interface and implemented it in SwitcherRequest to allow clearing execution records without affecting input entries. [1] [2]

API and builder enhancements:

• Added a keepExecutions flag and corresponding keepExecutions() method to SwitcherBuilder, allowing executions to be retained in memory. The throttle() method now automatically enables this. [1] [2] [3]
• Refactored flush() in SwitcherBuilder to resetInputs(), which now only clears input entries, separating input management from executions management. [1] [2]

Async execution logic:

• Updated AsyncSwitcher to use the new executions map and methods, ensuring consistent terminology and logic throughout asynchronous operations. [1] [2]

Code consistency and clarity:

• Updated imports, comments, and variable names across files to reflect the new terminology and improve code readability. [1] [2]

These changes collectively improve the clarity, maintainability, and usability of the switcher API, making execution management more explicit and easier to control.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud