Fix pre-commit formatting issues in pyth-token.mdx, starknet.mdx, and ton.mdx #901
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
Fixed pre-commit formatting issues in three MDX documentation files that were blocking commits:
pages/home/pyth-token.mdxpages/price-feeds/use-real-time-data/pull-integration/starknet.mdxpages/price-feeds/use-real-time-data/pull-integration/ton.mdxChanges made:
Type of Change
Areas Affected
pages/home/pyth-token.mdx- Import statement formattingpages/price-feeds/use-real-time-data/pull-integration/starknet.mdx- Tabs component code blockspages/price-feeds/use-real-time-data/pull-integration/ton.mdx- Tabs component code blocksChecklist
pre-commit run --all-filesto check for linting errorsRelated Issues
Resolves the pre-commit failures mentioned in Slack #developer-relations
Additional Notes
The prettier formatting appears to prefer single-line code blocks within Tabs components. This is the main functional change to review - please ensure this renders correctly in the browser before merging.
Contributor Information