-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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 standalone components #15465
Comments
Tagging @cetincakiroglu as requested in the discussion mentioned above |
@alexciesielski I would be interested to help with this effort. Are you planning to work from top of docs to bottom, or alphabetically? Perhaps we can coordinate if you you're willing for an assist 🙏 if you'd rather solo that's cool too |
Lets wait for @cetincakiroglu first to give his initial review on the PR I opened and then we can coordinate afterwards |
@alexciesielski Could you please create a checklist in this issue so it would be easier to track which components are done. I suggest you send PR's after we release v18, because we're doing some internal component changes and I don't want to break your valuable contribution. |
Describe the bug
As discussed here I volunteer to start the migraton of primeng components and directives to the new standalone API.
This issue is not a bug ticket, but simply an issue for the PR to reference.
Angular version
17.x
PrimeNG version
17.6.0
Expected behavior
Components and directives are standalone
The text was updated successfully, but these errors were encountered: