docs: add absolute paths to Pyth Pro integration meta.json #3221
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.
Summary
Updated the Pyth Pro integration documentation meta.json to use absolute paths instead of relative page names, following the pattern established in the pull integration documentation.
Rationale
This change addresses a request to standardize navigation paths across the documentation site. The pull integration section already uses absolute paths with descriptive labels (e.g.,
[in EVM contracts](/price-feeds/core/use-real-time-data/pull-integration/evm)), and this PR applies the same pattern to the Pyth Pro integration section.Using absolute paths helps:
How has this been tested?
Note: This change has not been manually verified in a running documentation server. Reviewers should verify that:
Link to Devin run: https://app.devin.ai/sessions/f86ad19486ae4a9196ec039b3756e403
Requested by: [email protected]