feat(api): expose Name and Type functions of TypeResolver #552
Conversation
This file contains hidden or 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
nrwiersma
reviewed
Jul 19, 2025
Comment on lines
121
to
123
| TypeOf(name string) (reflect2.Type, error) | ||
|
|
||
| NamesOf(typ reflect2.Type) ([]string, error) |
Member
There was a problem hiding this comment.
Please add comments to these.
nrwiersma
approved these changes
Jul 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Goal of this PR
Sometimes it can be useful to get the registered struct types from TypeResolver and instantiate empty structs for unmarshalling.
How did I test it?
Registering custom struct and then fetching it's type using modified library.