Skip to content
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 16 support to use standalone component and signals #101

Open
sheikalthaf opened this issue Sep 3, 2023 · 8 comments
Open

Angular 16 support to use standalone component and signals #101

sheikalthaf opened this issue Sep 3, 2023 · 8 comments
Labels
refactor A code change that neither fixes a bug nor adds a feature

Comments

@sheikalthaf
Copy link
Contributor

sheikalthaf commented Sep 3, 2023

Do you have any plan to update to angular 16, so that we can make use of Standalone components and signals.

I'm ready to raise a PR for this

@llorenspujol
Copy link
Contributor

Hi again @sheikalthaf !

Currently, there are no plans to update to Angular 16.
This is primarily because AFAIK, if we upgrade to Angular 16, users still with Angular 14 will not be able to use the latest version of this lib! But, staying in Angular 14, let's users from Angular 14 to Angular 16 use it perfectly.

That being said, if Angular 14 libraries are not compatible with Angular 17 (which is expected to be released soon), we may need to upgrade the Angular version to ensure the library's compatibility with Angular 17.

@llorenspujol llorenspujol added the refactor A code change that neither fixes a bug nor adds a feature label Sep 5, 2023
@sheikalthaf
Copy link
Contributor Author

Yes, then we can wait for Angular 17 update

@akalitenya
Copy link

@llorenspujol, Angular 14 does not work with nodejs 18. If I need to upgrade to node 18 with angular 16 - will I still be able to depend on current angular-grid-layout version (angular14)?

@Jeredian
Copy link

Hi, @llorenspujol
Are there any updates regarding Angular 17 support ?

@llorenspujol
Copy link
Contributor

@Jeredian Agreed, it is time to upgrade Angular Grid Layout to Angular 16 and export it as a standalone component. This way, full standalone apps can import AngularGridLayout.

Having said that, even though Angular Grid Layout is currently written with Angular 14, it remains compatible with Angular 17, as far as you import it into an NgModule.

In resume, I am open to PRs for upgrading to Angular 16 (not Angular 17), with Angular Grid Layout exported as a standalone component. You may want to take it @sheikalthaf

@devglrd
Copy link

devglrd commented Apr 3, 2024

@llorenspujol Did you have open the PRs ?

@jelle-ingambh
Copy link

Is anything planned regarding Angular 16 / 17 / 18?

@sheikalthaf
Copy link
Contributor Author

sheikalthaf commented May 28, 2024

@Jeredian Agreed, it is time to upgrade Angular Grid Layout to Angular 16 and export it as a standalone component. This way, full standalone apps can import AngularGridLayout.

Having said that, even though Angular Grid Layout is currently written with Angular 14, it remains compatible with Angular 17, as far as you import it into an NgModule.

In resume, I am open to PRs for upgrading to Angular 16 (not Angular 17), with Angular Grid Layout exported as a standalone component. You may want to take it @sheikalthaf

@llorenspujol Created the PR for v15 and v16 versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactor A code change that neither fixes a bug nor adds a feature
Projects
None yet
Development

No branches or pull requests

6 participants