protoc: parser rejects explicit use of map_entry option (#13479)
This addresses #13441. Second try, now with more internal fixes. This preserves the similar check at the _point of use_ of invalid messages in `DescriptorBuilder` (and there's an existing test that verifies that check still works). But it adds another check in the parser, to catch this error at the _point of definition_ of an invalid message. And the corresponding test is updated: we no longer need a usage of the message to catch the error, and the reported position is the definition of the option, not the usage site of the message. The way this works feels kinda gross, but I wasn't sure of a better way to do it. The only place we know for certain that it was an explicit option (vs. auto-added by the parser when synthesizing a map entry message) is when after processing the message body, we can look at the uninterpreted options. So that's what this does. If you have ideas on better/cleaner approaches, I'd be happy to revise. Closes #13479 PiperOrigin-RevId: 557199190pull/13552/head
parent
9702adf6c8
commit
8f5929230d
3 changed files with 29 additions and 3 deletions
Loading…
Reference in new issue