-
Notifications
You must be signed in to change notification settings - Fork 178
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
Implement atom.services based linter v2 api #387
Comments
As per #411 we should consider including documenting a theme api as part of this process. |
Wasn't active on atom for a long time, just checked the atom/atom#5165 it looks awesome! I let you start, and will try to find the time for a little help next week :) |
@dmnd what you think about this? |
Moving to the new services API sounds pretty good to me.
In #282 we discussed linters that lint the actual file in the filesystem instead of a temporary copy. Maybe you could have two separate methods |
Also, I wonder if @bolinfest has opinions about this |
I was playing around with this in #432, but I'm not happy with what's there yet. |
I'm not sure if I should comment on this one or on #432. I was wondering if the linter could also provides, through a service, an access to the linter defined for an editor. I was about to start working on a linter plugin for the minimap and I was struggling to find how to access and be notified of the errors/warning raised by a linter so that I can display them in the minimap. |
Closing this issue as It was replaced by #546 |
V 2.0 api spec
lint(selectedSubstringToBeLinted, sourceFileName)
returns promise for an array of 'lintError's or just the array if done synclintError
range?
atom range object defining the range to which the error applies optional if only point providedpoint?
atom point [row, col] of the error if a linter can't find the range this will be expanded based on the local scope at that pointmessage
level
error levelexecutableLinter
(provides support for executing on the command linenodeExecutable
(uses BufferedNodeProcess)The text was updated successfully, but these errors were encountered: