excaped characters break selector detection with tailwind v3

Open
#299 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, tailwindcss
Domain
frontend, web-dev

Research direction

Start by reading the linked postcss/postcss-nested issue and reproduce the Tailwind v3 selector-detection case described here. The issue names no source file or test; done means escaped characters no longer break selector detection, with a regression test covering that case.

Written by the indexing model from the issue text.

Description

related to https://github.com/postcss/postcss-nested/issues/169

Dominant language
JavaScript
Stars
214
Forks
63
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from postcss/postcss-selector-parser

All issues in postcss/postcss-selector-parser

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.