Update fixed_rate channel format to use milliseconds consistently in docs #3269
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
Updates the subscription channel format from
1sto1000msacross Pyth Pro documentation to match the correct API format and ensure consistency.Files changed:
payload-reference.mdx: Updatedfixed_rate@1stofixed_rate@1000msin the subscription channels tablehow-lazer-works.mdx: Updated channel types list from(50ms, 200ms, 1s)to(50ms, 200ms, 1000ms)Rationale
The subscription channel for 1-second updates should use the millisecond format (
1000ms) for consistency with the other channel formats (1ms, 50ms, 200ms).How has this been tested?
This is a documentation-only change. Verified that the changes are applied correctly in both files.
Human Review Checklist
fixed_rate@1000msmatches the actual API channel nameLink to Devin run: https://app.devin.ai/sessions/2c23630013a140ea86b94f8d7ac1a64f
Requested by: Nidhi Singh (nidhi@pyth.network) / @nidhi-singh02