Set explicit component names across the application
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 .
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 .