Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Session for the strategy interfaces #410

Open
quaat opened this issue Jan 11, 2024 · 0 comments
Open

Remove Session for the strategy interfaces #410

quaat opened this issue Jan 11, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@quaat
Copy link
Contributor

quaat commented Jan 11, 2024

This a proposal of an enhancement to the OTEAPI-CORE project that could streamline the development process and improve the overall architecture. The proposal is centered around simplifying the strategy implementation by removing the session object from the strategy interface. The service, or a core-module, can have the responsibility for reading and updating the session information.

Proposed Change:
Remove the session object from the strategy interface. Instead, we can centralize the logic for reading and updating the session to the OTEAPI service. This change would lead to a cleaner and simpler strategy implementation, remove the need for boilerplate code for configuration updates and error handling.

@CasperWA CasperWA added the enhancement New feature or request label Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants