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 standalone components #15465

Open
alexciesielski opened this issue May 6, 2024 · 4 comments
Open

Angular standalone components #15465

alexciesielski opened this issue May 6, 2024 · 4 comments

Comments

@alexciesielski
Copy link
Contributor

alexciesielski commented May 6, 2024

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

@alexciesielski alexciesielski added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 6, 2024
@alexciesielski
Copy link
Contributor Author

Tagging @cetincakiroglu as requested in the discussion mentioned above

@kyjus25
Copy link
Contributor

kyjus25 commented May 8, 2024

@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

@alexciesielski
Copy link
Contributor Author

Lets wait for @cetincakiroglu first to give his initial review on the PR I opened and then we can coordinate afterwards

@cetincakiroglu cetincakiroglu removed the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label May 30, 2024
@cetincakiroglu
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants