mirror of
https://github.com/react/react-native-devtools-frontend.git
synced 2026-10-09 21:28:43 +08:00
This reverts commit 1e08ee816b.
Reason for revert: tree is closed due to errors https://ci.chromium.org/ui/p/devtools-frontend/builders/ci/Stand-alone%20Linux/8169/overview
Original change's description:
> Update stylelint to 14.0.1
>
> This also upgrades PostCSS to 8.3.11.
>
> DISABLE_THIRD_PARTY_CHECK=Updating Stylelint configuration
> R=szuend@chromium.org
>
> Bug: none
> Change-Id: I606540b03509d7c6e73f3d490327cd4174e03d31
> Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3259541
> Reviewed-by: Simon Zünd <szuend@chromium.org>
> Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Bug: none
Change-Id: Icb1c02b41dbccc3b4fc5760f5dd0b78eca078b61
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/3263399
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Owners-Override: Alex Rudenko <alexrudenko@chromium.org>
Commit-Queue: Alex Rudenko <alexrudenko@chromium.org>
1.8 KiB
1.8 KiB
Working on syntaxes
Please help us enhance and debug the syntaxes we use in stylelint:
To contribute to a syntax, you should:
- Familiarize yourself with PostCSS's how to write custom syntax guide.
- Use the
syntax: *labels to identify which syntax is behind an issue. - Go to the repository for that syntax.
- Read their contributing guidelines.
Workarounds
Fixing bugs in syntaxes can take time. stylelint can work around these bug by turning off autofix for incompatible sources. Autofix can then remain safe to use while contributors try to fix the underlying issue.
Current workarounds
stylelint currently turns off autofix for sources that contain:
nested tagged template literals (issue #4119)
Add a workaround
To add a new workaround, you should:
- Add code to
lib/lintSource.jsto detect the incompatible pattern. - Add a corresponding test to
lib/__tests__/standalone-fix.test.js. - Document the workaround in
docs/developer-guides/syntaxes.md.