Open limpo1989 opened 1 year ago
This does seem like it should be expected behaviour but I don't know if there's anywhere in documentation saying that this is the expected behaviour. It seems to me that there should/could be some sort of setting that enables this globally.
I agree with @jaitaiwan, if we want to mimic the behavior of other go standard packages like json
, unexported fields are to be ignored. A flag can help maintain backward compatibility, to avoid breaking things. @limpo1989 are you willing to submit a PR?
Is there an existing issue for this?
Current Behavior
create a structInfo but the always inculde unexported field
https://github.com/gorilla/schema/blob/5fca2dce7a3a9cde2cd764a822ae373b4aaaaece/cache.go#L129-L139
Expected Behavior
create a structInfo but the skip unexported field
Steps To Reproduce
No response
Anything else?
No response