DioxusLabs/taffy

Lint or validate HTML fixtures in CI

Open

#421 opened on Apr 10, 2023

View on GitHubContributor guide
 (0 comments) (1 reaction) (0 assignees)Rust (192 forks)github user discovery
build systemgood first issue

Repository metrics

Stars
 (3,189 stars)
PR merge metrics
 (Avg merge 15h 41m) (25 merged PRs in 30d)

Description

What problem does this solve or what need does it fill?

Our test fixtures are humanly typed HTML.

  • There has been some cases of typos in the html which produces invalid tests. #352
  • There was also a case of a missing semicolon somewhere, but I can't seem to find the PR or commit.

What solution would you like?

  • Some form of lint or validation in CI to ensure that the HTML is correct and without obvious flaws. This would help verify that our test results are correct and can be trusted (more).

What alternative(s) have you considered?

Do nothing, it's not a large cause of issues at the moment.

Contributor guide

Research direction
Add a CI step to validate HTML fixtures using a tool like HTMLProofer or W3C validator. Integrate it into the existing GitHub Actions workflow.
Tech stack
rust
Domain
devopstesting
Issue type
DevOps
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitCI/CD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70