Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Content] add JSON linting (automatic formatting) to JavaScript Guidelines #667

Open
possumbilities opened this issue Sep 16, 2022 · 2 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on

Comments

@possumbilities
Copy link
Contributor

possumbilities commented Sep 16, 2022

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-lint directly within repo

Additional context

@possumbilities possumbilities added 🟩 priority: low Low priority and doesn't need to be rushed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository labels Sep 16, 2022
@nsundriyal62
Copy link

i want to work on this little bug....
can you please assign to me.

@TimidRobot
Copy link
Member

@nsundriyal62 - Contributions are always welcomed. Please see Contribution Guidelines — Creative Commons Open Source for how we manage issues and PRs (we generally don't assign issues prior to resolution).

@TimidRobot TimidRobot moved this to Triage in Applications Sep 10, 2024
@TimidRobot TimidRobot moved this to Backlog in WebDev Sep 17, 2024
@TimidRobot TimidRobot moved this from Backlog to Triage in WebDev Sep 17, 2024
@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Sep 19, 2024
@possumbilities possumbilities moved this from Triage to Backlog in WebDev Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on
Projects
Status: Backlog
Development

No branches or pull requests

3 participants