Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Declutter infoview tests. #104
Declutter infoview tests. #104
Changes from 5 commits
8ceae98
f535de4
45ed26e
376fb56
c7c2e73
74e5bc7
cc4e5d4
20ce933
882a875
aa8b0db
1ae1809
9c6eac8
05fcb4d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This seems quite fragile to me because it adds global mutable state to all infoview-touching test runs. Would really prefer if we avoided doing that, we're already struggling with #94 showing us we have too much mutable state.
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.
This is something that you'd "opt-in" to on certain tests, and should be backwards compatible with the way we did things before (see e.g.
infoview/lsp_spec.lua
). ISTM that mutable state is pretty much the only way to get this kind of coverage, and the mutable state before was just littered throughout the tests themselves rather than centralized in a helper (not to mention being hopelessly incomplete).Did you perhaps mean #93? I'm pretty sure at this point the best way to handle it would be to:
infoview/run_spec.lua
.nvim-lua/plenary.nvim
that allows tests to early-abort as soon as anit()
fails, so only the first error is shown.