-
Notifications
You must be signed in to change notification settings - Fork 86
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
highcharts v12 fix #493
base: master
Are you sure you want to change the base?
highcharts v12 fix #493
Conversation
@@ -124,6 +124,6 @@ | |||
}, | |||
"peerDependencies": { | |||
"ember-source": ">= 3.28.0", | |||
"highcharts": ">= 5.0.0" | |||
"highcharts": ">= 12.0.0" |
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.
This would be 100% a breaking change. Not sure what would mean it wrt/ release strategy of this addon?
} | ||
|
||
if ( | ||
this.args.chartOptions?.chart?.type === 'treegraph' || | ||
this.args.chartOptions?.chart?.type === 'treemap' | ||
) { | ||
const Treemap = await import('highcharts/modules/treemap'); | ||
Treemap.default(Highcharts); | ||
await waitForPromise(import('highcharts/modules/treemap')); |
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.
I can't tell if the waitForPromise
is necessary for the few cases where it's missing, but I think it's a good idea to have it unified.
- Those two need some special treatment for some reason
Note: The re-render once checkbox is checked, because the test suite is happy. So I guess it will be an issue in my consuming app. |
- Sorry, no idea what it wants.
Issue: ``` You cannot set `staticHelpers`, `staticComponents`, or `staticModifiers` if you have set `staticInvokables`. Delete these configs to continue. ``` Related PR: https://github.com/miguelcobain/ember-yeti-table/pull/473/files Discussion: https://discord.com/channels/480462759797063690/491905849405472769/1328757079510487071
@@ -203,80 +203,59 @@ export default class HighCharts< | |||
*/ | |||
async _importHighchartsDeps() { | |||
if (this.args.mode === 'Map') { | |||
Highcharts = await waitForPromise(import('highcharts/highmaps')); | |||
//@ts-expect-error No idea, sielnt TS |
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.
I'm sorry, but no idea what it wants and don't see a cheap way to find out. Not ideal, but solves the problem.
- Not sure why would we want to assign the HighChart to module scope - This way it's tracked, so i guess(?) it might help with the initial render issue - Also so many things were named `Hightcharts`, so this helps
- Somehow there is a difference on my localhost for a consuming app using vite, because that one need the `default` unpack. - Tests pass, because they use webpack, IMO.
cc: @ahmadsoe can we 👀 this? |
@embroider/app-blueprint
app