JavaScript code does not follow the declared coding standard about cve-services

[david-waltermire-nist]

I don't believe this issue should be targeted at new developers. Instead, I believe it should be requirement of ALL developers. This should be thought of as technical debt. If a developer touches an existing file, they should be responsible for bringing it up to the standard. That way over time we will pay down the debt and have all source up to the standard.

There are also things we could to do to target the CI/CD, such as code reformatting and checking for PRs to ensure the coding standards are met.

[mattrbianchi]

Thanks @david-waltermire-nist. The idea of it being a good first issue at the time was that someone could look over the repo, fix linter errors, and be able to make a low risk pull request to the project. Similar to fixing typos in documentation, it can be a great way to get someone started in a project. I do understand how technical debt works and how a style standard should be obeyed by a dev team. I'll close this issue, as a CI/CD pipeline is coming which will contain a linter that applies the style standard we have chosen to branches and PRs.