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

Add linting to pull requests #1330

Open
1 of 4 tasks
trillium opened this issue Mar 12, 2023 · 3 comments · May be fixed by #1818
Open
1 of 4 tasks

Add linting to pull requests #1330

trillium opened this issue Mar 12, 2023 · 3 comments · May be fixed by #1818
Assignees
Labels
complexity: medium feature: Infrastructure Secrets, Prod and Dev setup, etc. role: devops size: 2pt Can be done in 7-12 hours

Comments

@trillium
Copy link
Member

trillium commented Mar 12, 2023

Overview

Devs on this team have differing eslint configurations. VRMS should standardize linting so that only relevant changes show up in commits, standardizing things like:
import {foo} from './foo' vs
import { foo } from './foo'

Action Items

  • Research a linting system
    • Use ESLint and Prettier
  • Add that linting system to VRMS
  • Test to see if new system is working

Resources/Instructions

@juliagab56 juliagab56 added this to the 3.01 Existing Features milestone Jul 5, 2023
@jbubar jbubar added size: 2pt Can be done in 7-12 hours and removed x-size: 3pt labels Jul 13, 2023
@JackHaeg JackHaeg moved this to New Issue Approval in P: VRMS: Project Board Jun 13, 2024
@angela-lee1 angela-lee1 self-assigned this Jun 20, 2024
@angela-lee1 angela-lee1 removed their assignment Jul 29, 2024
@trillium trillium added the Close after Vite merge Issue that is no longer relevant after Vite merge and can be closed label Aug 15, 2024
@trillium trillium moved this from New Issue Approval to Icebox in P: VRMS: Project Board Aug 15, 2024
@JackHaeg JackHaeg moved this from Icebox to Prioritized Backlog in P: VRMS: Project Board Aug 27, 2024
@JackHaeg
Copy link
Member

@trillium please add additional Action Items to this issue

@JackHaeg
Copy link
Member

@trillium Closing now that Vite has been merged.

@JackHaeg JackHaeg closed this as not planned Won't fix, can't repro, duplicate, stale Sep 19, 2024
@github-project-automation github-project-automation bot moved this from Prioritized Backlog to Final QA (product) in P: VRMS: Project Board Sep 19, 2024
@trillium
Copy link
Member Author

Reopening this issue, close after vite merge was a miss-label and consistent linting still needs to be implemented.

@trillium trillium reopened this Sep 24, 2024
@github-project-automation github-project-automation bot moved this from Final QA (product) to New Issue Approval in P: VRMS: Project Board Sep 24, 2024
@trillium trillium moved this from New Issue Approval to Prioritized Backlog in P: VRMS: Project Board Sep 24, 2024
@trillium trillium added feature: Infrastructure Secrets, Prod and Dev setup, etc. complexity: medium and removed Close after Vite merge Issue that is no longer relevant after Vite merge and can be closed feature: Github Actions labels Oct 15, 2024
@bkmorgan3 bkmorgan3 self-assigned this Dec 23, 2024
@trillium trillium linked a pull request Jan 6, 2025 that will close this issue
@JackHaeg JackHaeg moved this from Prioritized Backlog to In progress in P: VRMS: Project Board Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: medium feature: Infrastructure Secrets, Prod and Dev setup, etc. role: devops size: 2pt Can be done in 7-12 hours
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

7 participants