Walk and traverse should give context

Open
#89 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
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
css, typescript
Domain
compilers

Research direction

Start at the walk and traverse entry points and determine how optional context can expose the parent atrule, parent rule, and nesting depth. Done means selectors and declarations can identify the relevant surrounding constructs, including @keyframes and @supports, with the issue checklist satisfied.

Written by the indexing model from the issue text.

Description

annoyance

Add optional context to walk/traverse so a selector can know if it's inside a @keyframes, a declaration knows if it's inside a @supports, etc etc.

  • Parent atrule
  • parent rule
  • nesting depth
Dominant language
CSS
Stars
4
Forks
0
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 projectwallace/css-parser

All issues in projectwallace/css-parser

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.