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
Added an example section in the README. It is not that easily possible to add a note in the result as you suggested. Since it is not really clear to which node the comment belongs to. It would probably be possible to add another object containing only a comment, which would appear between the fields. Just give a hint if that would be sufficient.
I like the idea of adding kind of comments, but I would prefer to have it in a structured way.
For example https://github.com/favadi/protoc-go-inject-tag/blob/master/README.md#usage
use // @inject_tag: valid:"ip"
thus we could define required fields which needs to be handled in the front end (for example in forms) - as the required/optional parameter was dropped in proto3 // @inject_tag: required:"true"
which would be parsed as ....{ .... "required": true ... }
@inject_tag would be nice as I already use it for my go backend.
PS. the tag is always placed above the parameter
@lal12@maltegrosse
In fact, as long as the method of annotation is fixed, you can determine which annotations this is.
I'm also very familiar with regular expressions now, and writing this is relatively simple.
To give a suggestion, it is best to put an example.proto file in the library, so that it is easy to understand.
The text was updated successfully, but these errors were encountered: