fix: allow response types to contain unexported fields #278
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.
So far using a type as
Bodyon a response type containing unexported fields results in a panic:As I am using
ent(entgo.io) that is subpar, because the structs generated byentcontain unexported fields (in this caseconfig, which triggered the panic above).Creating proxy types would really break the experience, so it's not really an option.
And anyway I don't see why
humawould not want to support such structs as it seems to me there is no drawback in this simple fix suggested - but as I am new tohumaand its codebase I might just not see it 😉.Feedback would be appreciated.