-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change default behavior of resolve bibtex strings #8382
Conversation
Discussion: Invert logic And resolve fields only for the following list: TODO: Double braces in Changelog |
add field month to string resolving |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small nitpick regarding the negation - and two additional fields. 😇
* 'main' of github.com:JabRef/jabref: Replace master with main
…gResolving * 'stringResolving' of github.com:JabRef/jabref: Fix typos
I would now like to add test cases for the fields mentioned in the fixed issues. I know, It's "only" a preference (mocking) thing. However, I would like to have more tests to ensure that nothing breaks if we touch this part of the code at a later time. |
Do you want to test the FieldWriter with the mentioned fields in this PR or do you want to test the preferences if they return the right fields? I don't think the latter would be meaningful at all... Btw., this PR is still a draft... |
* upstream/main: Fix plural s in library properties tab (#8402)
- Add org.jabref.logic.bibtex.FieldWriter#BIBTEX_STRING_START_END_SYMBOL - !doNotResolveStrings -> resolveStrings
failing fetcher test is grobid |
I added the BibTeX field content of the three linked issues as tests (verbatimely). |
I am not sure if your negation change doesn't break anything |
Side note: I find
|
The only thing, I did not touch is the storing in the registry. There, the negegation is still stored. |
@@ -163,7 +168,7 @@ private String formatAndResolveStrings(String content, Field field) throws Inval | |||
} | |||
|
|||
private boolean shouldResolveStrings(Field field) { | |||
if (!preferences.isDoNotResolveStrings()) { | |||
if (preferences.isResolveStrings()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldResolveStrings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow-up PR 😇
After looking again at the changes, it looks good and I will merge it now |
Fixes #7010
Fixes #7012
Fixes #8303
CHANGELOG.md
described in a way that is understandable for the average user (if applicable)