Migrate schema page to Schema component and refactor layout#1001
Merged
Migrate schema page to Schema component and refactor layout#1001
Conversation
|
Size Change: +67 kB (+3.4%) Total Size: 2.04 MB
ℹ️ View Unchanged
|
|
Visit the preview URL for this PR (updated for commit bcf220f): https://docusaurus-openapi-36b86--pr1001-hs3r0ou8.web.app (expires Wed, 27 Nov 2024 14:21:28 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: bf293780ee827f578864d92193b8c2866acd459f |
Contributor
|
hi @sserrata, |
Member
Author
|
Hi @ahelmy, got sidetracked but was stuck on how to handle the differences in |
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
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.
Description
Migrates to new
Schematheme component for rendering schemas in schema pages and refactors layout as described in #996. Also allows use ofcreateSchemaPageMDwhen defining markdown generators.Motivation and Context
Ensures consistency in how schemas are represented across API and schema pages.
How Has This Been Tested?
See deploy preview