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
Fix async middleware #2164
Merged
Merged
Fix async middleware #2164
Changes from 3 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
65cb6a7
fix: handle result of async middleware
jly36963 6a99fb1
cleanup
jly36963 1d35513
Merge branch 'main' into fix-async-middleware
jly36963 bef63e2
Merge branch 'main' into fix-async-middleware
jly36963 fca98f4
Simplify test
jly36963 0d8d0d4
Merge branch 'main' into fix-async-middleware
bcoe 1d829e8
Merge branch 'main' into fix-async-middleware
jly36963 1c2718f
Merge branch 'main' into fix-async-middleware
bcoe File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -281,6 +281,33 @@ describe('middleware', () => { | |
} | ||
}); | ||
|
||
// Addresses: https://github.com/yargs/yargs/issues/2124 | ||
// This test will fail if the result of async middleware is not treated like a promise | ||
it('treats result of async middleware as promise', done => { | ||
const input = 'cmd1 -f Hello -b world'; | ||
yargs(input) | ||
.command( | ||
'cmd1', | ||
'cmd1 desc', | ||
yargs => | ||
yargs | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I had to read this a few times, I'm wondering if it would be worth simplifying to exactly the minimal case outlined in the regression:
I don't have a strong opinion though, if your goal was to exercise parts of the codebase that weren't covered in the above example. |
||
.option('foo', {type: 'string', alias: 'f', required: true}) | ||
.option('bar', {type: 'string', alias: 'b', required: true}) | ||
.middleware(async argv => { | ||
await new Promise(r => setTimeout(r, 5)); | ||
return argv; | ||
}, true), | ||
_argv => { | ||
done(); | ||
} | ||
) | ||
.fail(msg => { | ||
done(new Error(msg)); | ||
}) | ||
.strict() | ||
.parse(); | ||
}); | ||
|
||
it('runs before validation, when middleware is added in builder', done => { | ||
yargs(['mw']) | ||
.command( | ||
|
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.
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.
I would be tempted to write a more specific test to #2124
"Using the strict option in combination with an async middleware, which is applied before the validation, does not result in unknown command"
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.
I simplified the test. I kept the
done
logic, because Mocha will pass this test before the unhandled promise would cause it to fail. If there's a regression, this test will fail becausedone
will get called twice, and one of the executions will have an error passed as an argument