projectwallace / projectwallace/projectwallace.com

🎗️ stylelint: use defensive-css plugin

Open
#250 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

platform: code improvement
Dominant language
Svelte
Stars
3
Forks
0
Avg merge
1d 7h
Merged PRs (30d)
11

Description

Probably smart to opt-in only to what's useful to me https://github.com/yuschick/stylelint-plugin-defensive-css

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.

Research direction

Start by locating the repository's Stylelint configuration and review the linked stylelint-plugin-defensive-css project to identify which rules are useful here. Define the opt-in rule set and verify that the configuration loads successfully without introducing unwanted warnings.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
tooling
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.