-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
docs: enhance how references are generated #5805
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
What
Previously, we generated references in isolation of one another. This resulted in many duplicate pages in our documentation. For example, if an element in the JS Client references an entity, it creates a new documentation page for that entity rather than use the existing entities documentation.
The change introduced by this PR changes the process of generating references so it's no longer done in isolation. The changes include:
medusa
andtypes
packages, as most other references/packages depend on items imported from these packages. This ensures that other references don't create new documentation for items within those packages._merger
Typedoc configuration that generates a merged documentation from the JSON references of other references.generate:references
script works by running the merger configuration after all specified references are generated.References are also re-generated in this PR to resolve any possible errors arising in the documentation.