Skip to content

chore: split lint and lint-fix targets into frontend and backend#6222

Open
DanielRyanSmith wants to merge 1 commit intomainfrom
split-lint-targets
Open

chore: split lint and lint-fix targets into frontend and backend#6222
DanielRyanSmith wants to merge 1 commit intomainfrom
split-lint-targets

Conversation

@DanielRyanSmith
Copy link
Copy Markdown
Collaborator

Resolves #6212

Overview

Splits the make lint and make lint-fix targets into separate frontend and backend targets to improve developer workflow.

Root Cause / Motivation

Currently, running make lint checks both the Python backend and the TypeScript/JavaScript/Lit frontend simultaneously. When developers are only modifying one part of the stack, running all linters adds unnecessary overhead and slows down local iteration. Separating these into distinct targets allows developers to run only the linters relevant to their current work, while preserving the main lint and lint-fix targets for complete checks (e.g., in CI or pre-commit workflows).

Detailed Changelog

  • Makefile:
    • Created lint-frontend and lint-fix-frontend targets containing prettier, eslint, tsc, and lit-analyzer commands.
    • Created lint-backend and lint-fix-backend targets containing pylint and ruff commands.
    • Updated the main lint and lint-fix targets to depend on their respective frontend and backend sub-targets.
    • Added new targets to the .PHONY declaration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Split lint command in Makefile to separate Python and Frontend/TypeScript linting

1 participant