-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: Ambiguous term definition priority #269
Merged
Merged
Conversation
This file contains 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
…ber of other terms used from the glossary.
… of once per file.
This reverts commit d0f0d47.
chore: Refactor. Improve performance by implementing 'linking by ID' and term-based auto linking in the same tree-traversal. This keeps the number of traversals by the linkifier at 2, again. The second traversal will now be the new traversal for revisiting term occurrences after having collected statistics on how many terms of particular glossaries have been mentioned and using those statistics to priortize links for terms with multiple definitions.
Updating baseline due to different JSON serialization of class properties.
When disambiguating ambiguous terms in parent sections take terminology use in subsections into account. Before this change parent sections have been evaluated in isolation ignoring glossary references in subsections. For example when using ambiguous terms in an introductory paragraph of a chapter disambiguation did only look at glossary popularity in the introductory paragraph of the chapter ignoring glossary popularity in subsections of the same chapter. Now it disambiguates parent sections based on an aggregation of glossary references in the introductory paragraph and also all subsections of the chapter.
about-code
added a commit
that referenced
this pull request
Aug 23, 2023
* Fix perSectionDepth value range * Fix perSectionDepth not being initialize with documented default.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 #271