Skip to content

chore: tidy up codebase and enforce linting and formatting standards #24130

@nick-popovic

Description

@nick-popovic

Summary

The codebase requires an audit to ensure it fully adheres to the engineering standards and testing conventions defined in GEMINI.md. This includes verifying test isolation practices, consistent code styling, and project-wide type safety.

Areas of Focus

  • Test Environment Isolation: Identify test files that may be directly manipulating process.env instead of using the recommended Vitest vi.stubEnv methods.
  • Styling and Linting: Audit the repository for any linting or formatting violations that deviate from the project's ESLint and Prettier configurations.
  • Type Integrity: Ensure all packages within the monorepo pass comprehensive type checking.

Rationale

Regularly aligning the codebase with established standards prevents technical debt, reduces test flakiness, and ensures a consistent development experience across the repository.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/platformIssues related to Build infra, Release mgmt, Testing, Eval infra, Capacity, Quota mgmtstatus/need-triageIssues that need to be triaged by the triage automation.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions