Skip to content

feat: biome#3110

Open
AbhishekA1509 wants to merge 3 commits into
developfrom
feat/biome
Open

feat: biome#3110
AbhishekA1509 wants to merge 3 commits into
developfrom
feat/biome

Conversation

@AbhishekA1509

Copy link
Copy Markdown
Member

Description

This pull request migrates the project's code formatting and linting setup from ESLint and Prettier to Biome, a new all-in-one code formatter and linter. The changes remove the previous ESLint and Prettier configuration files, update VSCode settings to use Biome for formatting and fixing issues, and adjust the lint-staged configuration to use Biome for code checks.

Migration to Biome for Formatting and Linting

  • Tooling and Configuration Updates:

    • Removed .eslintrc.js and .prettierrc.js files, eliminating all ESLint and Prettier configuration and rules from the project. [1] [2]
    • Cleaned up .eslintignore by removing all ignore patterns and file references, as ESLint is no longer used.
  • Editor and Workflow Integration:

    • Updated .vscode/settings.json to set Biome as the default formatter for TypeScript, TypeScript React, and JSON files. Enabled format-on-save and configured code actions to use Biome for fixes, while disabling Prettier and ESLint extensions.
    • Changed .lintstagedrc to run biome check --write instead of eslint for staged file checks, ensuring consistent formatting and linting in pre-commit hooks.

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas

- Updated type annotations for state variables and function parameters in ChartDeploymentHistory, DevtronStackManager, and other components to enhance type safety.
- Replaced legacy `==` comparisons with strict `===` where applicable.
- Simplified error handling by removing unused error variables in async functions.
- Improved accessibility by adding `alt` attributes to images and ARIA labels to elements.
- Refactored event handlers to avoid passing unnecessary parameters.
- Cleaned up unused variables and imports across multiple files.
- Added comments to suppress specific linting rules for legacy code.
@github-actions

Copy link
Copy Markdown

Some linked issues are invalid. Please update the issue links:\nIssue # in is not found or invalid (HTTP }404).\n

@github-actions github-actions Bot added the PR:Issue-verification-failed PR:Issue-verification-failed label May 18, 2026
Comment thread src/components/dockerRegistry/Docker.tsx
Comment thread src/components/dockerRegistry/Docker.tsx
@sonarqubecloud

Copy link
Copy Markdown

Quality Gate Failed Quality Gate failed

Failed conditions
4 Security Hotspots
B Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

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

Labels

PR:Issue-verification-failed PR:Issue-verification-failed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants