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

Refactor ExecutionContext, RuntimeService, etc. to clarify t heir semantics and handling of global state and code. #374

Open
vinjana opened this issue Nov 16, 2023 · 0 comments

Comments

@vinjana
Copy link
Contributor

vinjana commented Nov 16, 2023

ExecutionContext has much too much functionality for a single class.

Needs to be split up into multiple classes.

  • File IO (directories, files, locks, buffers) only because of logging needs. Keep it with FileSystemAccessProvider.

  • Loggging using standard logging framework removes the need to centralize here.

  • On the other hand, keep global state, like BEJob states and executed jobs and commands here (for now).

  • Overall, clarify the exact purpose of RuntimeService, ExecutionContext, FileSystemAccessProvider, Configuration and

  • clean up all the mess!

@vinjana vinjana moved this to Backlog in RoddyCore May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

1 participant