Adding glossary plugin#1713
Conversation
|
@mcclowes is attempting to deploy a commit to the Codat Team on Vercel. A member of the Team first needs to authorize it. |
There was a problem hiding this comment.
This PR is being reviewed by Cursor Bugbot
Details
Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.
To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.
| { | ||
| "term": "Data source", | ||
| "definition": "An external platform (such as QuickBooks, Xero, or a bank) that Codat integrates with to pull or push financial data.", | ||
| "relatedTerms": ["Connection", "Integration"] |
There was a problem hiding this comment.
Bug: Related term references non-existent glossary entry
The "Data source" term's relatedTerms array includes "Integration", but no term with that name is defined in the glossary. This orphaned reference could result in broken links or rendering errors when the glossary plugin attempts to display related terms, depending on how the plugin handles missing references.
| presets: [ | ||
| [ | ||
| "classic", | ||
| "docusaurus-plugin-glossary/preset", |
There was a problem hiding this comment.
Bug: Replacing classic preset may break site functionality
The preset was changed from "classic" to "docusaurus-plugin-glossary/preset", but the glossary plugin's package metadata shows it doesn't depend on or include @docusaurus/preset-classic. The configuration still passes classic preset options (docs, blog, theme, sitemap) which may be silently ignored by the glossary preset. This could cause the documentation, blog, theming, and sitemap functionality to stop working. The retained @type {import('@docusaurus/preset-classic').Options} comment further suggests this replacement may be unintentional.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
@pzaichkina Plugin I built which is like the old terminology stuff we had. Feel free to use, just have a look and expand on the defined terms.
Note
Adds the glossary plugin to Docusaurus, configures it at
/glossary, and introduces an initial glossary dataset.docusaurus-plugin-glossary/presetand configureglossarywithglossary/glossary.jsonand route/glossaryindocusaurus.config.js.glossary/glossary.jsoncontaining initial terms (API, Connection, Company, Data source, Webhook, Sync, SMB, Bank Feeds, Link, REST).docusaurus-plugin-glossarytopackage.json.Written by Cursor Bugbot for commit edf7f0d. This will update automatically on new commits. Configure here.