ni / ni/javascript-styleguide

CSS linting

Open
#98 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
9
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Cases to consider:

  • .css files
  • .scss files
  • CSS that's written in TS like FAST's css template literal
  • .css files in Blazor projects

Contributor guide

Open the contributing guide

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

The issue defines four CSS-linting cases: .css files, .scss files, CSS in FAST TypeScript css template literals, and .css files in Blazor projects. Start by reviewing the repository’s existing JavaScript and TypeScript linting setup; done means the chosen approach covers all four cases with documented verification.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, scss, typescript
Domain
frontend, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.