fix: fixed init_lexicon#53
Merged
Merged
Conversation
chasetmartin
approved these changes
Aug 1, 2025
chasetmartin
left a comment
chasetmartin
left a comment
Collaborator
There was a problem hiding this comment.
It's working for me! I'll push my address_type changes to data manager.
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
2 participants
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.
Why
This PR fixes initialization of the lexicon from the lexicon.json. There was an issue when adding a term to multiple categories.
How
Implementation summary - the following was changed / added / removed:
init_lexiconto either add or use and existing term. If the term exists it still will try to add to a categoryNotes
Any special considerations, workarounds, or follow-up work to note?
N/A