-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[docs] The error style rule is a pseudo-class #19555
[docs] The error style rule is a pseudo-class #19555
Conversation
No bundle size changes comparing 21e9f1d...b64fcb2 |
@TommyJackson85 Could you fix the CI :)? |
@oliviertassinari from running `yarn lint:ci`
```yarn lint:ci
yarn run v1.16.0
$ eslint . --report-unused-disable-directives
/Users/thomasjackson/Desktop/Software projects/Open Source Projects/material-ui/docs/src/modules/components/AdInHouse.js
1:1 error Configuration for rule "react/jsx-no-target-blank" is invalid:
Value {"allowReferrer":true} should NOT have additional properties.
react/jsx-no-target-blank
54:9 error Using target="_blank" without rel="noopener noreferrer" is a security risk: see https://mathiasbynens.github.io/rel-noopener react/jsx-no-target-blank
/Users/thomasjackson/Desktop/Software projects/Open Source Projects/material-ui/packages/babel-plugin-unwrap-createstyles/test/unwrapCreateStyles.test.js
1:26 error Unable to resolve path to module 'babel-plugin-tester/pure' import/no-unresolved
✖ 3 problems (3 errors, 0 warnings)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.```
Is this why it's broken?
Managed to remove the first error (1:1) by changing it to an empty object instead `{}`
Would removing target="_blank" and rel="noopener noreferrer" fix the next?
Unsure if these changes are recommended in the long run and might cause other errors, unless you can tell me otherwise.
Will keep updating this comment when ever I make changes.
… On 4 Feb 2020, at 17:33, Olivier Tassinari ***@***.***> wrote:
@TommyJackson85 Could you fix the CI :)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@TommyJackson85 Try 1. upgrading yarn to a more recent version 2. running a new install. |
Reinstalled yarn and ran yarn docs:api to try and fix cicircle fail and other fails. |
It looks great. Well done. |
Closes #19551
Changed text description for styles applied on errors, from "Styles" to "Pseudo Class".