Update list.rs to include inscription and rune info #3766
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
fixes ordinals#3701 - I've added the /output/<OUTPOINT> fields to the `ord list` command into a section called 'list'. I also reordered the fields in the existing 'ranges' section to make more logical sense. There is a small amount of redundancy now with the list.sat_ranges vs ranges.start & end, and list.value vs ranges.size.
deleted commented test
raphjaph
requested changes
May 23, 2024
removing comment Co-authored-by: raph <[email protected]>
removing comment Co-authored-by: raph <[email protected]>
removing comment Co-authored-by: raph <[email protected]>
removing comment Co-authored-by: raph <[email protected]>
cryptoni9n
commented
May 23, 2024
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.
fixes #3701 - I've added the
/output/<OUTPOINT>fields to theord listcommand into a section called "list'. I also reordered the fields in the pre-existing "ranges" section to make more logical sense. There is a small amount of redundancy now with the list.sat_ranges vs ranges.start & end, and list.value vs ranges.size. I figure that this is acceptable and better than changing the pre-existing ranges section, as some users may already be reliant upon those fields - but let me know if not and if further formatting or changes would be better.