Replaces Highcharts with Chart.js

[cbaudouinjr]

Closes #1002

Summary by CodeRabbit

• Refactor
  • Transitioned from Highcharts to Chart.js for improved performance and visual enhancements in chart rendering.

[coderabbitai]

Walkthrough

The project transitioned from using the Highcharts library to Chart.js for chart rendering. This change involved removing Highcharts from the dependency list, updating JavaScript asset dependencies, and modifying initialization scripts to accommodate Chart.js, aiming to improve maintainability, performance, and reduce potential licensing costs.

Changes

Files	Change Summary
Gemfile	Removed highcharts-rails gem
app/assets/javascripts/.../application.assets.js	Replaced highcharts with Chart.bundle
app/assets/javascripts/manage/application.js	Replaced setupHighcharts with setupChartJs
app/assets/javascripts/manage/lib/setupChartJs.js	Renamed function to setupChartJs from setupHighcharts

Related issues

• Replace Highcharts with Chart.js #1002: This PR directly addresses the key objectives outlined in the issue by replacing Highcharts with Chart.js, ensuring seamless transition and updating documentation and codebase as required for Chart.js integration.

🐇✨
In the realm of code, where charts do play,
A switch was made, Chart.js leads the way.
Out with the old, in with the new,
Smooth transitions, our aim is true.
Celebrate we shall, for the change is done,
A hop, a skip, under the coding sun.
🌟📊

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-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

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

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 1

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between ad8c264 and f707273.

Files ignored due to path filters (1)

• Gemfile.lock is excluded by: !**/*.lock

Files selected for processing (4)

• Gemfile (1 hunks)
• app/assets/javascripts/application.assets.js (1 hunks)
• app/assets/javascripts/manage/application.js (1 hunks)
• app/assets/javascripts/manage/lib/setupChartJs.js (1 hunks)

Files skipped from review due to trivial changes (1)

• Gemfile

Additional comments: 2

app/assets/javascripts/manage/application.js (1)

• 18-18: The call to setupChartJs correctly reflects the transition to Chart.js. Ensure that setupChartJs is properly adapted to Chart.js's API and configuration requirements.

app/assets/javascripts/application.assets.js (1)

• 17-17: The inclusion of Chart.bundle in the asset pipeline correctly aligns with the transition to Chart.js. Ensure that this bundle version supports all the features needed for your charting requirements.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between f707273 and b213f5d.

Files selected for processing (1)

• app/assets/javascripts/manage/application.js (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• app/assets/javascripts/manage/application.js