-
Notifications
You must be signed in to change notification settings - Fork 159
feat(timeout): allow to configure the timeout for queries #7
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
Merged
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
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.
This call isn't quite safe. What if
queryImpltakes other set of arguments, not justtextfollowed byoptions? The original idea was to propagate all the query options verbatim toqueryImpl. I would considerqueryImpl.length(the function arity) to see how many arguments it actually takes, and passed the respective slice ofargsto it; if there's one more argument remaining, that's our Cypress commandoptionswithtimeoutand potentially other stuff such aslog: false.Relying on function arity may be unreliable if the
queryImpluses variable number of...args(i.e.arguments) instead of defining all arguments explicitly.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.
Good point. However, I prefer to have a single options object, so there's no need to keep in mind which options go into which object. Do you agree?
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 prefer the
...argsfor stuff like this if we can get away with it.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.
So if I understand this correctly, the function arity of our command function is the function arity of the query function + 1, right?
If the query function takes two arguments;
textandoptionsandoptionsis optional, you'd have to pass in("text", undefined, { timeout: 10000 })to set a timeout?I prefer the API to have a single options object. For that to work and still use
...args, we'd have to make the assumption that theoptionsparameter is the last argument. In that case, I can retrieve it usingargs[args.length -1]and destructure it like already in the PR. So I agree that...argsis better, but I think the command function shouldn't have an extra options object just for the Cypress related options. What are your thoughts on that?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.
Honestly I don't care all that much. Let's just go with what you have here and we can change it in the future if it needs changing. I think I'm good with this PR as-is :)
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.
Okay, whatevs. I'm just saying that
queryImplis not guaranteed to be that generic to always take(doc, text, options).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.
Hmmm... I think that's right. In that case, below where we're using
textandoptionsinmessage, do we need to make that more generic somehow to support different APIs?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.
Yes, that, too. There was a generic solution before: just pass all the
argsformessage(Cypress can handle arrays in themessageas far as I remember).