Feature/create services interfaces #521
Merged
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.
See #519
The event service has an example use-case to notify of a working directory update across the application and lower coupling (in this case, it drops an explicit dependency to an UI component). I will be using it more as I find other use-cases in the code base, didn't look too much.
This PR also explicitly set components names. This might not seem like much now but it should be a first step toward allowing feature discovery later down the road.
As an aside : I tried to implement a ServiceLoader but was not happy with it as it did not make use of spring features and would just have made the application more bloated. Will give it another go when i find a more fitting design. For now, it feels like autowired components should be configured as attributes instead of being provided in constructor to limit the bloat seen in #272 .