-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Disallow importing Joi client side #55018
Conversation
Looks like |
The first one looks like it is only used on the server, so it should be save to move it to a The second one will be resolved by #54910 (should be done soon) |
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.
Tested locally, code LGTM. Thanks for adding this, JL!
Yep, should be good to move that one. |
I'm not sure if we want the v8.0.0 label on this PR. We may be dropping support for IE11 in 8.0.0. If that decision is made, will someone remember to change the eslint rule? |
@LeeDr that makes sense to me! I've also added a TODO to the lint rule. |
@elasticmachine merge upstream |
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.
LGTM
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
Summary
After this blocker: #54888 arose blocking 7.6 QA (and a previous case of
joi
causing an issue in IE11 (#36493)).This seems like something an automated check can help with.
How to review
joi
in x-pack plugin publicjoi
in oss plugin publicScreenshot
Piggy backing off of existing eslint rules