Hide exports that aren't used in frontend from the documentation.#3480
Hide exports that aren't used in frontend from the documentation.#3480benchristel wants to merge 2 commits intomainfrom
Conversation
… used in frontend from the docs website
…'t used in frontend from the documentation.
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review to trigger a review and subscribe this PR to future pushes, or @claude review once for a one-time review.
Tip: disable this comment in your organization's Code Review settings.
🗄️ Schema Change: No Changes ✅ |
🛠️ Item Splitting: No Changes ✅ |
|
Size Change: 0 B Total Size: 497 kB ℹ️ View Unchanged
|
npm Snapshot: PublishedGood news!! We've packaged up the latest commit from this PR (902a29f) and published it to npm. You Example: pnpm add @khanacademy/perseus@PR3480If you are working in Khan Academy's frontend, you can run the below command. ./dev/tools/bump_perseus_version.ts -t PR3480If you are working in Khan Academy's webapp, you can run the below command. ./dev/tools/bump_perseus_version.js -t PR3480 |
jeremywiebe
left a comment
There was a problem hiding this comment.
Makes sense. It's pretty easy to reverse any of these changes to make them visible in the API docs. Thanks for more cleanup!
| } from "./parse-perseus-json"; | ||
| /** @hidden */ | ||
| export { | ||
| parseAndMigrateUserInputMap, |
There was a problem hiding this comment.
Is this not used by the service?
Summary:
We want the documentation to be tidy so other teams can use it. This PR removes
clutter from unused exports.
Issue: LEMS-4014
Test plan:
View the generated docs site.