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
Support ConditionalExpressions in dry-error-messages rule #11917
Conversation
existentialism
commented
Aug 5, 2020
•
edited by gitpod-io
bot
edited by gitpod-io
bot
Q | A |
---|---|
License | MIT |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit bf958cd:
|
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/26902/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for doing this! Mind adding some tests?
I didn't do this originally because it felt brittle, but maybe we could enforce that the argument must either be a reference or a conditional where both the truths and falsy expressions are references to the imported error constant?
Sorry, wasn't clear - the suggestion to enforce what is allowed doesn't have to be a blocker for this! Just a thought I had. Ideally, someone new to the project would be able to come in and the linter would teach them exactly what we're expecting (to hopefully save reviewers from having to think about it!). |
@kaicataldo added some tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks!