Angular standalone components

[alexciesielski]

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]

Tagging @cetincakiroglu as requested in the discussion mentioned above

[kyjus25]

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

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

[cetincakiroglu]

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

[github-actions]

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

[kyjus25]

Reopen - will be resumed at the completion of new theming API in v18