Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow jest-validate to print deprecation warnings for CLI flags
See original GitHub issueDo you want to request a feature or report a bug? Feature
What is the current behavior?
When jest-validate was created in #2524, it came with support for printing deprecation warnings in configuration.
If the current behavior is a bug, please provide the steps to reproduce and
either a repl.it demo through https://repl.it/languages/jest or a minimal
repository on GitHub that we can yarn install and yarn test.
N/A
What is the expected behavior? It would be great if we could also print deprecation warnings for CLI flags in the same way. Currently unknown flags throws (which makes sense to catch typos), but it would be great to alert users of removed (or altered) options in a semver-compliant way.
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system. Jest@master
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I agree. Separate issue, though
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.