feat(encode): accept any input type #67
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
Previously, only a *yaml.Node was accepted, which required the caller to encode arbitrary data to an AST node before they would be able to use the Encoder. This saves them that step while remaining backwards-compatible for callers still passing in AST nodes. Signed-off-by: Dan Luhring <dluhring@chainguard.dev>
imjasonh
approved these changes
Aug 7, 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.
Previously, only a
*yaml.Nodewas accepted, which required the caller to encode arbitrary data to an AST node before they would be able to use theEncoder. This saves them that step while remaining backwards-compatible for callers still passing in AST nodes.