Frontend operations center begin (#208)

[amengus87]

• chore: Update RaagService to include SiloRepository (chore: Update npm dependencies to latest versions #197)

• Renaming route home to operations-center

• Operations Center updates

• Adding fake endpoints on backends to allow auth

• On 404 error, deliver index.html (SPA)

• Begin using pre-commit to lint over files

• chore: Refactor OpenAiCompatibleV1ApiControllerTest to improve code readability and remove unused imports

• chore: Add ErrorHandlerController to handle errors and deliver index.html on 404 error (SPA)

• Updating frontend dependencies

• chore: Update operations center to fetch numbers on page activation

• refactor: Rename header-banner.vue to infrastructure-overall.vue and card-data.vue to jvm-cards.vue

• Improving how to retrieve env vars for Testing

• Frontend : adding infrastructure overall

• chore: Update npm dependencies to latest versions

• chore: Add error handling for delivering index.html on 404 error (SPA)

• refactor: Update icons in jvm-cards.vue for better visual representation

• chore: Add SystemMonitoringServiceTest for system monitoring functionality

Issue

Change

General checklist

• There are no breaking changes
• I have added unit and integration tests for my change
• I have manually run all the unit and integration tests in the module I have added/changed, and they are all green

• I have added/updated the documentation

Summary by CodeRabbit

• New Features

  • Introduced automated pre-commit checks to ensure code quality.
  • Added new API endpoints for authentication and dashboard metrics.
  • Implemented a System Monitoring Service for real-time performance metrics.

• Improvements

  • Enhanced routing structure by replacing the home route with the operations center.
  • Updated linting commands to enforce stricter rules for cleaner code.
  • Improved localization schema for infrastructure-related terms and system metrics.

• Bug Fixes

  • Refined error message handling in API requests for clearer context.

• Documentation

  • Updated localization files to reflect new terms and metrics for improved usability.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update introduces significant enhancements in the project’s structure and functionality, focusing on code quality checks, improved API organization, and refined localization. Key changes include implementing pre-commit hooks for automated linting, restructuring API endpoints for better clarity, and enhancing the dashboard interface with new metrics. Additionally, the project adopts stricter linting rules and updates several dependencies, promoting maintainability and supporting a robust development workflow.

Changes

File(s)	Change Summary
.devcontainer/postStart.sh, .devcontainer/pre-commit	Added pre-commit hooks to automate Gradle tasks for linting and code checks, enhancing code quality assurance.
.github/workflows/build.yml	Updated CI/CD pipeline to include separate linting jobs for frontend and backend, simplifying the testing structure and improving maintainability.
.gitignore, backend/.gitignore	Added .env.local to ignore local environment configurations, promoting clean version control.
backend/build.gradle	Added spring-dotenv dependency for improved environment variable management; removed jacoco configuration, indicating a focus shift.
backend/src/main/java/...	Introduced new controllers (AuthAppApiController, DashboardAppApiController) for API interactions; added error handling and improved response structures.
backend/src/main/resources/.env.local.example, backend/src/main/resources/.env.properties	Added new environment variable for OpenAI API key, supporting integration in local configurations.
frontend/.env	Changed home route variable to operations-center, affecting application navigation.
frontend/package.json, frontend/packages/axios/package.json	Updated linting commands and dependency versions to enhance code quality and maintain up-to-date libraries.
frontend/src/service/api/...	Refactored API service modules for better organization and updated endpoint paths to include /api/app, improving clarity in API interactions.
frontend/src/views/operations-center/...	Introduced new Vue components and restructured existing ones to visualize infrastructure metrics, enhancing the dashboard functionality.
frontend/src/typings/...	Updated TypeScript definitions to support new API structures and removed obsolete properties, streamlining the codebase.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant Git
    participant CI/CD
    participant Backend
    participant Frontend

    Developer->>Git: Commit changes
    Git->>Git: Run pre-commit hooks
    Git->>CI/CD: Trigger build
    CI/CD->>Backend: Run lint and tests
    CI/CD->>Frontend: Run lint and tests
    Backend->>CI/CD: Report results
    Frontend->>CI/CD: Report results
    CI/CD->>Developer: Send notifications

Loading

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud