JabRef
Customizable AI templates
Now, all LLM templates can be customized by users. Previously, only the system message was customizable in a limited way.
I used Apache Velocity template engine.
Mandatory checks
~- [ ] Change in CHANGELOG.md described in a way that is understandable for the average user (if applicable)~
~- [ ] Tests created for changes (if applicable)~
- [x] Manually tested changed features in running JabRef (always required)
- [x] Screenshots added in PR description (for UI changes)
- [x] Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
- [x] Checked 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 to the documentation repository.
Side comment: This refs https://github.com/koppor/jabref/issues/392, where we first wanted Apache Velocity - but then wanted Thymeleaf (and did not want Apache FreeMarker).
I think it I necessary now to finally create an ADR now for the template engine. Please create a simple one, with your decision drivers for velocity and we can fill in the others for the next dev-call to decide on it together.
I think we need to decide on it, since we should not have multiple templating engines running in favor of resources.
I think it I necessary now to finally create an ADR now for the template engine.
Coming from https://github.com/JabRef/jabref/pull/11900, Velocity was the right choice. We need to improve the ADR itself, but it is good enough to show that this was the right choice.
@InAnYan Can you resolve the conflicts? I think, then, this can go in - and https://github.com/JabRef/user-documentation/pull/519 can also be merged?