feat(docs): add ADR for DI
Closes https://github.com/JabRef/jabref-issue-melting-pot/issues/590
Just added an ADR.
Steps to test
No steps to test. Just check the contents.
Mandatory checks
- [x] I own the copyright of the code submitted and I license it under the MIT license
- [x] I manually tested my changes in running JabRef (always required)
- [/] I added JUnit tests for changes (if applicable)
- [/] I added screenshots in the PR description (if change is visible to the user)
- [/] I described the change in
CHANGELOG.mdin a way that is understandable for the average user (if change is visible to the user) - [x] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.
You modified Markdown (*.md) files and did not meet JabRef's rules for consistently formatted Markdown files. To ensure consistent styling, we have markdown-lint in place. Markdown lint's rules help to keep our Markdown files consistent within this repository and consistent with the Markdown files outside here.
You can check the detailed error output by navigating to your pull request, selecting the tab "Checks", section "Source Code Tests" (on the left), subsection "Markdown".
- [ ] TODO: We use
@Injectonly inViews, not inViewModels. And this again helps in testing, asViewModeluses constructor-based DI
- [ ] TODO
@Injectfor JAX-RS services - there, we usejakarta.inject.Injectand hk2:org.glassfish.hk2.api.ServiceLocator
https://github.com/dlsc-software-consulting-gmbh/FxmlKit