Skip to content

Conversation

@tembleking
Copy link
Member

@tembleking tembleking commented Dec 9, 2025

This introduces several key enhancements to the project configuration and codebase, focusing on modernization and maintenance.

🚧 Development

  • Added a small configuration to launch both a mini-frontend and a mini-backend to ensure with just start the UI is working properly, without the need of a full blown backstage installation. This allows faster feedback loop with auto-reload of the changes.

📦 Refactor: MUI v5 Migration

  • Migrated all UI components from Material-UI v4 (@material-ui/core, @material-ui/icons) to MUI v5 (@mui/material, @mui/icons-material).
  • Updated package.json dependencies and component imports to reflect this change.
  • Updated AGENTS.md documentation to reference the new styling library.

🧹 Dependency Cleanup

  • Removed unused dependencies and devDependencies from package.json to improve project hygiene and reduce install time.

🛠️ Tooling & CI Enhancements

  • Justfile:
    • Added audit command (yarn npm audit) for security checks.
    • Updated clean command to ensure dependencies are installed first.
  • Pre-commit: Updated hooks to utilize just lint and just test, ensuring consistency between local development and pre-commit checks.

… adds more diverse mock data entries to the Sysdig API client for development and testing purposes. Encountered and did not resolve persistent ESLint configuration errors related to @typescript-eslint/no-unused-expressions. A separate task is needed to address the linter setup.
…ues in SysdigPostureFetchComponent.tsx\n\nThis commit refactors SysdigPostureFetchComponent.tsx to ensure React Hooks are called unconditionally, addressing the react-hooks/rules-of-hooks error. It also fixes various other linting issues in the file, including prefer-const, no-var, eqeqeq, prefer-template, and no-else-return. Additionally, it updates package.json and yarn.lock to properly include eslint, @typescript-eslint/* and eslint-formatter-friendly as dev dependencies, which resolved the initial linter setup errors.
…ues in SysdigVMPipelineFetchComponent.tsx\n\nThis commit refactors SysdigVMPipelineFetchComponent.tsx to ensure React Hooks are called unconditionally, addressing the react-hooks/rules-of-hooks error. It also fixes various other linting issues in the file, including prefer-const, no-var, eqeqeq, prefer-template, and no-else-return.
…ues in SysdigVMRegistryFetchComponent.tsx\n\nThis commit refactors SysdigVMRegistryFetchComponent.tsx to ensure React Hooks are called unconditionally, addressing the react-hooks/rules-of-hooks error. It also fixes various other linting issues in the file, including prefer-const, no-var, eqeqeq, prefer-template, and no-else-return.
…ues in SysdigVMRuntimeFetchComponent.tsx\n\nThis commit refactors SysdigVMRuntimeFetchComponent.tsx to ensure React Hooks are called unconditionally, addressing the react-hooks/rules-of-hooks error. It also fixes various other linting issues in the file, including prefer-const, no-var, eqeqeq, prefer-template, and no-else-return.
…s the remaining linting issues across multiple files:\n- : Fixes by changing to for .\n- : Fixes , , and issues in and .\n- : Addresses a comprehensive list of linting issues, including , , , , , , , , , , , and .\n- : Fixes errors in block comments.
… addresses the final specific linting issues:\n- : Fixes errors for and components.\n- : Fixes by replacing with for null checks.\n- : Fixes by removing a duplicate import and by adding a space after in a comment.
@tembleking tembleking self-assigned this Dec 9, 2025
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.

2 participants