Skip to content
New issue

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

XML Parser Used. #10

Open
bd82 opened this issue Aug 15, 2019 · 2 comments
Open

XML Parser Used. #10

bd82 opened this issue Aug 15, 2019 · 2 comments

Comments

@bd82
Copy link

bd82 commented Aug 15, 2019

Hello.

I see this project is using SAX to parse XML and then perform additional logic on the tags output stream.

Does SAX provide full parsing capabilities for the use case of building editor services?

The reason I am asking is because I've implemented a Parser building library in JS:

Which provides editor related infrastructure capabilities:

  • Fault Tolerance / Error Recovery (Does not stop on the first error).
  • Full syntax information collection (e.g location of closing tags).
  • Syntactic Content Assist
  • Multiple start rules.
  • ...

There is also an XML grammar example:

Feel free to contact me if this is of interest to you.

Cheers.
Shahar.

@rogalmic
Copy link
Owner

Actually, SAX is very low level, which i was looking for at the time. The purpose of this extension is to have basic XML functionality (tag complete, linter, format) with small dependency list (I was not able to find such extension for vscode).

I will check this Chevrotain, for now keeping this open.

@bd82
Copy link
Author

bd82 commented Aug 15, 2019

Some potentially relevant productive examples in the context of LSP / Editor Services.

  • MetaBase Expression Language + Auto Complete

  • ArgDown LSP

  • Java Prettier Plugin Prettier + Formatter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants