[Feature Request] SLDS Validator Support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- tooling
Research direction
Start by reviewing the existing code analyzer engine integrations and the SLDS Validator VS Code extension behavior. Define which validator rules should be exposed in the pipeline and how they become reportable requirements. Done means SLDS Validator checks are available through the analyzer with documented rule behavior and coverage for the integration.
Written by the indexing model from the issue text.
Description
Product Area
An Engine
Your Need or Problem
SLDS Validator is available as an extension, but many of the recommendations would make sense to report on from a pipeline perspective, where certain rules could even be requirements.
It would be great to add this as an engine in code analyzer
Your Desired Solution
Add SLDS validator (as in vscode extension) to code analyzer
Alternatives Considered
not having a CLI validation and relying on good will of developers
Additional Context (Screenshots, Files, etc)
No response
Workaround
No response
Urgency
Low
- Dominant language
- TypeScript
- Stars
- 240
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/code-analyzer
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
forcedotcom/code-analyzer#2094 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
forcedotcom/code-analyzer#2093 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
forcedotcom/code-analyzer#2091 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
forcedotcom/code-analyzer#2090 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
forcedotcom/code-analyzer#2101 ·
All issues in forcedotcom/code-analyzer
Similar issues
-
bug HemiStake
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
hemilabs/ui-monorepo#2413 ·
Maintainers usually reply within 1 day
-
component/ui framework/react kind/bug language/javascript
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
meshery/meshery#22216 · 3 comments ·
Maintainers usually reply within 1 day
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
paperclipai/paperclip#14982 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
lingdojo/kana-dojo#31515 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day