Fix saving preferences while AI API key is empty #11661
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.
Closes https://github.com/JabRef/jabref-issue-melting-pot/issues/511.
When you accept privacy policy for AI, AI features are enabled, but API key is empty.
If in this state you go to preferences, change some other preferences that you need (for example switching language), then preferences window won't allow this to do, because there is an empty API key.
What this PR does: even if API key is empty, we allow to save it empty. All logic will work okay after that, because empty API key is handled there, and as a last resort there
Mandatory checks
- [ ] Change inCHANGELOG.md
described in a way that is understandable for the average user (if applicable)- [ ] Tests created for changes (if applicable)- [ ] Screenshots added in PR description (for UI changes)