You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The testing-library/no-debug test also warns about using console.debug(), although there is a separate built-in test for that: no-console. I would like to allow console.debug() statements (our config contains "no-console": ["error", {"allow": ["debug", "warn", "error"]}]), but still keep testing-library/no-debug enabled for testing-library debug statements.
The text was updated successfully, but these errors were encountered:
Hello @srittau! Thanks for reporting this issue. Indeed, console.debug should be out of the scope of testing-library/no-debug. It should be easy to fix, I hope I can get back soon with the bugfix.
The
testing-library/no-debug
test also warns about usingconsole.debug()
, although there is a separate built-in test for that:no-console
. I would like to allowconsole.debug()
statements (our config contains"no-console": ["error", {"allow": ["debug", "warn", "error"]}]
), but still keeptesting-library/no-debug
enabled for testing-library debug statements.The text was updated successfully, but these errors were encountered: