-
-
Couldn't load subscription status.
- Fork 191
Open
Labels
✨ goal: improvementImprovement to an existing featureImprovement to an existing feature💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository🟩 priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed🧹 status: ticket work requiredNeeds more details before it can be worked onNeeds more details before it can be worked on
Description
Problem
There is not currently a consistent method by which to lint JSON across repositories
Description
The least intrusive route would be to create a singular repository with the right linting setup, and then a GH Action that would run, grabbing the config from that repo and applying the linting to various repos as part of a workflow.
This could be documented in the Guidelines, however if it was seamless enough it might not be necessary to be a part of the Guidelines and could instead run "behind the scenes" on trigger.
Alternatives
- utlize
npm-package-json-lintdirectly within repo
Additional context
Metadata
Metadata
Assignees
Labels
✨ goal: improvementImprovement to an existing featureImprovement to an existing feature💻 aspect: codeConcerns the software code in the repositoryConcerns the software code in the repository🟩 priority: lowLow priority and doesn't need to be rushedLow priority and doesn't need to be rushed🧹 status: ticket work requiredNeeds more details before it can be worked onNeeds more details before it can be worked on
Type
Projects
Status
Backlog