Skip to content

migrate frontend to chartjs 4 #277

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

pwoltschk
Copy link
Collaborator

To resolve issue #274, I had to migrate the project to Chart.js version 3+ to address the reported problem. Given the presence of several breaking changes in version 3, I opted to update to the latest available version and adjust the codebase accordingly. The migration involved some refactoring of the Chart.js integration, including registering components explicitly, modifying tooltip callbacks, and updating configuration options to align with the new API.

As a result of the update, the animation bug was successfully resolved, and the chart now functions as expected.
Please refer to the attached GIF for a demonstration of the updated chart behavior.

NugetTrendsBug3

@pwoltschk
Copy link
Collaborator Author

Hi @bruno-garcia could you may have a look?

Copy link
Member

@bruno-garcia bruno-garcia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for upgrading and fixing things!

@bruno-garcia
Copy link
Member

Also, CI fails because it requires a secret, that's not available on forks. I'll just merge it!
Sorry for the delay

@bruno-garcia bruno-garcia merged commit ebfcb6f into dotnet:main Feb 2, 2025
1 of 2 checks passed
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