-
Notifications
You must be signed in to change notification settings - Fork 110
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
Angular version support #312
Comments
Amazing! Welcome back! |
I'd be more than happy to do so if we find 2-3 volunteers! |
Check out ng16-dep-audit to see what dependencies need to change for the upgrade to Angular 16. I've noticed most libraries move to version matching i.e. Angular 16 and this package would be version 16 and so on. |
Yeah, I think matching the version of the package with the minimum supported Angular version sounds fair. I hope this suits everyone! If you have other suggestions please let me know, I'll wait for a couple more days before I merge and release 🙂 |
Welcome back! |
Can you mention anywhere in description which angular version support which version of this package. Currently I am looking for supported version with angular16. |
Just released a new version that supports Angular 16 an up 🎉 |
Thanks for the merge, Error: node_modules/angular-google-charts/lib/components/chart-editor/chart-editor-ref.d.ts:2:23 - error TS2688: Cannot find type definition file for 'projects/angular-google-charts/src/lib/components/chart-editor/chart-editor'. 2 ///
Error: node_modules/angular-google-charts/lib/components/chart-editor/chart-editor.component.d.ts:15:72 - error TS2694: Namespace 'google.visualization' has no exported member 'ChartEditor'. 15 get initialized$(): import("rxjs").Observable<google.visualization.ChartEditor>;
can you help us quickly, We are stuck in angular project migration due to this. |
Hi, I´m using this component with angular 19, can you tell me if it supports angular 19? |
I'm using Angular 19, no problem at all |
Hi, I can't get it to show me the graphics This is my main.ts
This is my html
This is component.ts
Could you help me please? |
Hi @Robinl2018, Your example seems to work for me! If you're still facing issues, please try to figure out whether it's a bug and open a separate issue if that's the case. Thanks 🙂 |
Hey everyone! First of all, sorry for not being as active during the last 1-2 years. I've been quite busy at work and didn't have much time to look into web development. As I now have some more time again, I'll try to dedicate some time and love to this package 🙂
First things first, I'll create a final release for Angular 12 with the current versioning (would be 2.2.4 then), supporting Angular 12-15. The next step will be to create a new release that aligns with the recent developments in the world of Angular (standalone components, mostly, but also the way overdue Ivy support (#144 and #257). This release will support Angular 16 and up.
However, I'm now thinking of how to approach versioning to be better prepared for future version changes of Angular. I've learned by now that it's important to only change the supported Angular version in major releases of the package to not break build systems (sorry) 😄 I'd like to keep supporting at least the 2 previous major Angular versions with this package (as is the convention by the Angular core team), but nevertheless integrate new approaches to Angular development as they appear.
Are there recommended approaches in the Angular world on how to handle this?
I'll close the other issues on version support in favor of this one:
The text was updated successfully, but these errors were encountered: