-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Add log: boolean option to cy.tick #15180
Comments
I don't see any reason why `cy.tick()`` wouldn't allow an options argument. Probably just an oversight. |
Awesome! I’ll try getting on that in the near future :) |
@emilgoldsmith I hope you don't mind but I went ahead and created a PR to address your issue. Let me know if that works for you. |
That’s just perfect, thank you Saturnino :)
…On Fri, 19 Mar 2021 at 17.36, Saturnino Abril ***@***.***> wrote:
@emilgoldsmith <https://github.com/emilgoldsmith> I hope you don't mind
but I went ahead and created a PR to address your issue. Let me know if
that works for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15180 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEKO66VKB6CODXUKFU7WFHLTEN4PZANCNFSM4YAZ5RFQ>
.
|
Woops, looks like I created a duplicate pr.. Can close.. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
What would you like?
Currently there is no log option on tick, as I had expected while working on customizing my log. Was wondering if it was an oversight or on purpose?
Why is this needed?
To align with the feature set surrounding allowing you to customize your log, most commands support this option so I was expecting this one to have it too, and would be nice to silence this one in a specific custom command I'm building though I'll of course live without it
The text was updated successfully, but these errors were encountered: