-
Notifications
You must be signed in to change notification settings - Fork 23
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
Remove highcharts dependency #2334
Remove highcharts dependency #2334
Conversation
{ | ||
path: 'chart-deprecated', | ||
component: ChartDeprecatedExampleComponent, | ||
}, | ||
{ | ||
path: 'chart', | ||
component: ChartExampleComponent, | ||
}, | ||
{ | ||
path: 'stock-chart-deprecated', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this line be removed too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It indeed should! I've removed it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, only one minor question before we are good to go 💯
Which issue does this PR close?
This PR closes #1578
What is the new behavior?
The highcharts dependency has been removed. All components along with specs, mocks, etc. has been removed. This means the two elements:
kirby-stock-chart-deprecated
&kirby-chart-deprecated
can no longer be used.Does this PR introduce a breaking change?
Migration guide
The new
kirby-stock
component should be used instead. It has types equivalent to the ones used in highcharts.Are there any additional context?
Checklist:
The following tasks should be carried out in sequence in order to follow the process of contributing correctly.
Reminders
Make sure you have implemented tests following the guidelines in: "The good: Test".Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).Review
Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)When the pull request has been approved it will be merged to
develop
by Team Kirby.