Vladimír Gorej

@vitaliy-sk I investigated and determined that the current behavior is correct. [request](https://github.com/JetBrains/http-request-in-editor-spec/blob/master/spec.md#32-request) requires a `new-line` terminal to follow immediately after `request-line`. Without it, the ambiguity will appear. This parser is...

Yeah, I'm seeing the same on this fixture: ```yaml swagger: "2.0" paths: /pet/adding-new-pets/testing-thelong-size-path-name/testing-thepath/testingthepathnameggggggggggggggggggggggggglllllllllllllla: {} ``` The worst thing is that the lexical analysis stops on long line and doesn't continue...

Parametrize the link renderer seems to be better and more flexible option

@handrews I created a implementation with formal ANBF grammar in https://github.com/char0n/openapi-path-templating. I did a couple of assumption, because of the fact that the templating is not defined very precisely. Hope...

Yes, good idea @buehlefs `Operation` description is good start and is using working already present in AsyncAPI 3.0.0 spec. > An operation describes a specific action an application can take...

Thanks for contribution. I'll try to look at it during the weekend.

Hi @mischnic, Ahh, interesting that parcel is implementing Stage 1 proposals. Anyway it's clear now why it happens. Thanks! I've adopted naming changes withing the code to void situation however...

Here is an example how [tree-sitter-json](https://github.com/tree-sitter/tree-sitter-json) produces it's CST. Given ```json {a* ``` The resulting CST would be: ``` Error Literal - { Error - a* ``` As we can...

@ikatyang thanks for describing the problem. That explains a lot. Error recovery and parsing the entire source string are two most important things that we were looking for with tree-sitter....

> A quick workaround would be to treat those invalid indent/dedent tokens as valid ones that make more sense in that position, though it'd result in treating invalid tokens as...