-
-
Notifications
You must be signed in to change notification settings - Fork 389
Add code actions for disabling a warning in the current file #1235
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
Conversation
The properties tested were previously unnecessarily strong and would break witht the addition of irrelevant code actions. We now don't care about position and total quantity of code actions, only that the ones we care about exist.
Fairly confident tests should pass now. Are we squash-merging these days? Commit history here is a bit noisy due to some carelessness on my part... |
@georgefst Mostly yes. Although some manual merges are done as normal merges, automated ones with "merge me" label are done as squash merges. |
... and we're done. Closes #571. There are a lot of tests which rely on the exact position in which a particular action happens to appear in the list returned by |
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.
Looks great, this is a nice feature and includes a solid test suite, thanks!
Previously known as haskell/ghcide#897.
Progress towards #705.