Alfred Fuller
Alfred Fuller
Great. Can you contact me via https://buf.build/links/slack?
Import cases: - empty import statement: `import "";` (done) - import statement without a trailing ';': `import ""` (done)
I considered several techniques like this (for example injecting a special cursor token), though anything that modifies the input will also make source positions inaccurate.
Only remaining issue from the original list is making a field with only a type work: ``` message Foo { my.type. } ```
New use case: - Missing field id: `int32 foo;`
I've look around a bit, and all I can find is the [c highlighting library](https://github.com/tree-sitter/tree-sitter/tree/master/highlight) and the [tree-sitter-web query interface](https://github.com/tree-sitter/tree-sitter/blob/master/lib/binding_web/tree-sitter-web.d.ts#L152C36-L152C36). I believe, if you feed in the [highlights query file](https://github.com/bufbuild/tree-sitter-cel/blob/main/queries/highlights.scm),...
Reading that issue, it looks like it might actually be possible bypass the regex based highlighter and use tree-sitter; though, tree-sitter-web also uses wasm, to its a lot to pull...
Note that the type checker is correct, and the underlying problem is that `{uint} in {list(uint)}` is not evaluating correctly, and always returns false for protobuf repeated uint fields. Though...
I've run into this issue as well.
protoyaml is not protojson and you cannot fuzz them like that for many reason.