Repository navigation
馃摑 Note field key case change in migration guide - #634
Merged
Merged
Conversation
v1 lowercased all field keys, v2 keeps them as written in the .bib file. Show how to get v1 behavior with the NormalizeFieldKeys middleware. Refs #629
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
As reported in #629 (comment), v1 lowercased all field keys, while v2 keeps them as written (
TitlestaysTitle, soentry["title"]raisesKeyError). The migration guide didn't mention this.Adds a note to "Accessing the library" showing how to get v1 behavior:
Snippet verified locally; docs build not run (Sphinx not installed here).
Refs #629