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
LUAFDN-784 Try to download all tools before erroring #62
LUAFDN-784 Try to download all tools before erroring #62
Changes from 17 commits
cf10cfb
adfa272
ccfcdfd
f2dab7b
5dcde1f
74213f0
10ba75d
18b405d
5f0aed0
faebb6d
f2f5a8f
907fdb5
bde37a8
7e3c6a8
8e36024
10bfa87
ae9b16b
878201d
379e14f
a13a6d6
7a04e31
546c86f
488b342
3655814
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 test ends up actually downloading these tools. Is there any way to mock downloading stylua and selene? I want to have a "successful" download alongside the failed ones.
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 possible yes but you will have to refactor the code to inject a custom ToolProvider implementation. This is probably easier to do within the
src
code. Tests intests
are considered at least integration level and so they cannot access private members. So if you refactor the code a little, you can write a unit test inmain.rs
that injects a memory only tool providerThere 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.
I think I'll just add an e2e test with the actual downloads and just test out the download failure here. I don't want the scope of this PR to get too large, so I might just file an issue to inject a mocked tool provider if there isn't one already.