no-debug also affects console.debug()

[srittau]

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.

[Belco90]

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.

[gndelia]

I think I can take this one

[github-actions]

🎉 This issue has been resolved in version 4.1.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀