Suggestion: suppress Cypress promise/async warnings

[FFdhorkin]

cypress-promise seems like it would improve the readability/maintainability of our test code significantly. We're using Cypress to test API endpoints, not an actual webpage, so many of the concerns Cypress raises in their "Commands are not Promises" blurb don't really matter, and the way Cypress can lead to many levels of indents can be painful.

However, all the warnings that Cypress spits out during usage of cypress-promise are somewhat of a nonstarter.

There's got to be some way to have cypress-promise suppress all of Cypress' warnings. (It'd be better to transpile, as you mentioned on #5, but I'd bet that'd be much more effort.)

[NicholasBoll]

Arg. 100% agree. I'm sure it is possible. I've tried a few times for several hours per attempt. I can't quite figure out the internal mechanisms enough to get this lib to work consistently or to remove the warning.

Warning is thrown here:
https://github.com/cypress-io/cypress/blob/7afe4f8c40e3c4166a4d1ba4a941248edf5329fc/packages/driver/src/cy/commands/connectors.coffee#L116-L120

Defined here:
https://github.com/cypress-io/cypress/blob/b6703aaec756ad58bdf4b2f3df3a3a1a9dbbc4f8/packages/driver/src/cypress/error_messages.coffee#L1324-L1335

[Dan503]

Maybe the solution is to raise an issue against Cypress to allow users to suppress the warning?