-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add lint on type and other improvements #145
Add lint on type and other improvements #145
Conversation
Apologies for how big this PR is. If you'd prefer it split up, I can do that. |
It is not that big. Could you please rebase it, I will continue review/test tomorrow? Thanks for the PR 💪🏻 |
Switched from exec to spawn to use stdin, and we don't have to worry about paths with spaces
Replaced TaskToken/CancelCallback with vscode CancellationToken due to running into queue issues Added output channel to see what the extension is doing to help w/ debugging onType is enabled by default for ameba >=1.6.3
saving a `.ameba.yml` in a workspace will clear all diagnostics from all documents and re-run ameba on them The latter allows for a very fluid experience of editing the config and seeing the errors in real time
b7521e2
to
5a2e88e
Compare
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
Co-authored-by: Sijawusz Pur Rahnama <[email protected]>
…pe config option lint-scope of file is how the ext currently behaves, clearing diagnostics if a file is closed and only linting open files lint-scope of workspace runs ameba over the entire workspace, not clearing them when a file is closed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's GTG from me, once the several remaining points are addressed.
I've actually made a few changes locally that will need review as well, primarily around onSave/onType config. I should be able to push in a few hours. |
Updated with most recent changes, also updated the description |
@nobodywasishere This PR got pretty big with the recent changes. It would be much easier to review it in parts, would it be possible for you to split it to smaller PRs in order to help with the process? |
Closes #89.
lint-trigger
that defaults totype
, but will be set tosave
for versions of ameba < 1.6.3lint-scope
that tells the extension how to treat the linterfile
is the current behavior of only running the linter on open files, and removing lints when files are closedworkspace
runs lints for the entire workspace, and doesn't remove them when the file is closed; I personally prefer this mode as it allows me to see lints for files I haven't touchedspawn
instead ofexec
as it's required to be able to write to stdinsemver
, which may or may not be desired; if it's not, its functionality can be rewritten locally.ameba.yml
will clear all diagnostics from all documents and re-run ameba on them to refresh their diagnostics with the new rules