prettier/prettier-atom

Change from prettier-stylelint to stylelint-prettier

Open

#866 opened on Aug 18, 2020

View on GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (764 stars) (106 forks)batch import
enhancementhelp wanted

Description

prettier-stylelint seems to be unmaintained. No updates for years.

For example this nasty bug https://github.com/prettier/prettier-atom/issues/718 probably won't be ever resolved in prettier-stylelint. But is already solved in stylelint-prettier.

That newer one stylelint-prettier seems very well maintained. Recommend switching to this one instead: https://github.com/prettier/stylelint-prettier

Contributor guide

Tech stack
javascript
Domain
toolingdeveloper experience
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.jsnpmbasic knowledge of linters
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
The contributor should first confirm that stylelint prettier is compatible with the existing prettier atom setup. Then, update package.json to replace prettier stylelint with stylelint prettier, update any configuration files (e.g., .stylelintrc) to use stylelint prettier instead, and run the existing test suite to ensure no breaking changes. The issue has no comments or linked PRs, so the approach is straightforward.
Change from prettier-stylelint to stylelint-prettier · prettier/prettier-atom#866 | Good First Issue