We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've just added this project grammar to https://mingodad.github.io/parsertl-playground/playground/ (select Protobuf3 parser under examples then click Parse to see the parser tree).
Protobuf3 parser
Parse
I hope it can help develop/debug/extend/test/document the grammar used in this project.
I did some changes there:
proto_content : * proto
proto_content_oom
Any feedback is welcome !
The text was updated successfully, but these errors were encountered:
Oh that's cool, I looked the other day and it wasn't working but now it is! Very neat :)
Sorry, something went wrong.
I just found an example that this grammar doesn't seem to accept in https://github.com/electric-sql/electric/blob/main/protocol/satellite.proto :
enum SatAuthHeader { reserved 1; // Required by the Protobuf spec. UNSPECIFIED = 0; }
There is no rule to accept reserved 1;.
reserved 1;
Changing the grammar like this seems to fix the problem:
enum_body_content : option | enum_value | reserved //<<< adding this rule ;
See documentation here https://protobuf.dev/programming-guides/proto3/#reserved
The above can be tested on https://mingodad.github.io/parsertl-playground/playground/ 👍
No branches or pull requests
I've just added this project grammar to https://mingodad.github.io/parsertl-playground/playground/ (select
Protobuf3 parser
under examples then clickParse
to see the parser tree).I hope it can help develop/debug/extend/test/document the grammar used in this project.
I did some changes there:
proto_content : * proto
removed and addedproto_content_oom
)Any feedback is welcome !
The text was updated successfully, but these errors were encountered: