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

[Feature request] output error locations and messages in parsable format (such as JSON, XML, etc.) #60

Closed
sim590 opened this issue Jan 19, 2019 · 4 comments
Labels
enhancement New feature or request
Milestone

Comments

@sim590
Copy link

sim590 commented Jan 19, 2019

It would be very nice if this plugin could output information in such a manner. This could enable writing some plugins for text editors to point out errors in the file directly.

An already existing and relevant plugin that comes to mind is vimtex. A new feature highlighting errors and showing them in the quickfix (or location) window would be a perfect addition to this plugin.

@sim590
Copy link
Author

sim590 commented Jan 19, 2019

If that's of any interest to you, I have opened a feature request on Vimtex's repository. As I have pointed out on that page, some vim plugin already interfaces with LanguageTool directly. Therefore, I shall go and check how they do it before saying that #60 is actually relevant. May be it's not needed... Would you know?

@sylvainhalle
Copy link
Owner

That would be nice indeed, and not so hard to implement. Will flag this as a feature for the next release.

@sylvainhalle sylvainhalle added this to the v0.8 milestone Jan 19, 2019
@sylvainhalle sylvainhalle added the enhancement New feature or request label Jan 19, 2019
@sim590
Copy link
Author

sim590 commented Jan 19, 2019

Thanks for your quick response!

After checking the Vim plugin for LanguageTool, I have found that it uses LanguageTool's XML output. If textidote can do the same, then reusing the plugin's code will be even easier.

@sylvainhalle
Copy link
Owner

XML is deprecated, so it should be JSON

sylvainhalle added a commit that referenced this issue Aug 5, 2019
As mentioned in an earlier comment, I won't support XML output. LT's own website tells users not to use XML anymore (http://wiki.languagetool.org/http-server#toc4), and it seems that LT no longer produces XML output since at least 2016.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants