Add more custom format specifiers #85
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
Closed
heaths
requested changes
Feb 8, 2024
|
I added tests, see this commit. |
heaths
approved these changes
Feb 9, 2024
heaths
changed the title
heaths
force-pushed
the
more-custom-formats
branch
4 times, most recently
from
dd33e89
to
09c9802
Compare
heaths
force-pushed
the
more-custom-formats
branch
from
09c9802
to
9a6970f
Compare
|
v1.9.0 with this change has been released. Thank you again! |
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.
Add
{x0}through{x10}custom format specifiers to enable finer format customizations.Also add a
{nl}specifier to insert a newline for multiline formats.Example custom format:
// __NAME__ {B}{nl}const __NAME__: GUID = GUID {data1: 0x{x0}, data2: 0x{x1}, data3: 0x{x2}, data4: [0x{x3}, 0x{x4}, 0x{x5}, 0x{x6}, 0x{x7}, 0x{x8}, 0x{x9}, 0x{x10}]};Result: