fkling / fkling/astexplorer

[Enhancement][Postcss] : Requesting to add postcss-value-parser and postcss-selector-parser for postcss transformer

Open
#466 3 comments 0 reactions 0 assignees View on GitHub
feature request
Dominant language
JavaScript
Stars
6.5k
Forks
772
PR merge metrics
No merged PRs in 30d

Description

**Current**
Currently, the postcss parser doesn't provide this out of the box. So most of the `value` node of the graph remains as it is like the value written.

**Enhancement**
There is a [`postcss-value-parser`](https://github.com/shellscape/postcss-values-parser/tree/master) already present I was thinking if it can be added as an opt-in thing so that those values can be transformed to nodes.

**Alternative**
I couldnt find any other parser or default from postcss.

But I do think it will help a lot to those who are writing postcss-plugins

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the PostCSS transformer integration and reviewing how parser output is represented. Check the postcss-value-parser and postcss-selector-parser references in the issue, then define the opt-in behavior and verify that values and selectors are exposed as transformed nodes without changing the default output.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.