pytest-dev / pytest-dev/pytest-html

SASS/SCSS/CSS linter

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

Nobody has claimed this yet.

Infrastructure
Dominant language
Python
Stars
779
Forks
260
PR merge metrics
No merged PRs in 30d

Description

At the moment i write this issue there is no liter used for StyleSheets.

#385 introduces use of for SASS/SCSS
and also introduces a linter. The linter is arguable -
see https://github.com/pytest-dev/pytest-html/pull/385/files#r531829346
see https://github.com/pytest-dev/pytest-html/pull/385#discussion_r531829346

This issue is a reminder, to come back to the topic of a StyleSheets linter.

  • The linter must validate source styles (css/sass/scss)
  • The linter should validate generated styles

candidates

see also: https://github.com/pytest-dev/pytest-html/pull/385/files/8873bfb399a063747f19409f730cfb94cc944bd8#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9

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 reviewing PR #385 and the linked discussion about its linter, then compare the listed sass-lint, scss-lint, and stylelint candidates. Determine how source styles and, if feasible, generated styles should be validated. Done means the chosen approach lint-checks the required stylesheet sources and documents or implements generated-style validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, sass, scss
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.