Allow extra option locations in source info when building an image #2803
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.
This is a feature I added to
protocompile
last year because it was easy to do because of the way thatprotocompile
parses the option values.(It can't easily be done in
protoc
because it doesn't actually parse message literals: it scans through the source to the end of the value, looking for a matching{
that closes the opening}
, and just stores the tokens in a string value. Later, the value is interpreted by using the Protobuf text format to unmarshal that string of tokens into a message.)Apparently, I forgot to enable it in
buf
last year. I did this specifically for things like linting custom options (like the protovalidate options), and we can see it pays off a bit in the updated test.The motivation for me remembering to add this today, so many months later, is so that we can capture more of the comments when rendering custom options in generated docs.