Move RFC4506 reference in XDR documentation higher #1252
Merged
Conversation
This file contains 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
add a missing link
|
Preview is available here: |
2 similar comments
|
Preview is available here: |
|
Preview is available here: |
Shaptic
approved these changes
Feb 3, 2025
|
Preview is available here: |
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.
What
Move the RFC 4506 reference higher in the XDR doc.
Why
For a lot of folks in the ecosystem who have only seen XDR used on Stellar and nowhere else, it's easy to think this is just some weird format that Stellar uses. But it's a well defined format in RFC4506, which is cheap to mention straight up at the top of the page. Mentioning it early helps to shape the context on what the format is.