You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No where in the README (the only documentation I can find), does it say that the fields of the structs need to be public. That's a basic and easy concept to add to the documentation.
Describe the solution that you would like.
Documentation on using the tools
Describe alternatives you have considered.
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Hey @bconn98 , thanks for bringing this up - it's a good suggestion. Would you mind opening up a pull request with what you had in mind and linking it to this issue?
I think that it is implicit in how Go works. I understand that for folks new to Go it might not be obvious — but there's no way for an ext library (except maybe reflect but haven't looked into that) to see the private fields of a struct. I'm okay with it being documented, I don't think it can hurt... Just noting I don't think it's strictly necessary.
Is there an existing feature request for this?
Is your feature request related to a problem? Please describe.
No where in the README (the only documentation I can find), does it say that the fields of the structs need to be public. That's a basic and easy concept to add to the documentation.
Describe the solution that you would like.
Documentation on using the tools
Describe alternatives you have considered.
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: