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

Convert Angular components to use standalone api-s #127

Open
eneajaho opened this issue Nov 12, 2022 · 4 comments
Open

Convert Angular components to use standalone api-s #127

eneajaho opened this issue Nov 12, 2022 · 4 comments
Labels
content specific to `content` directory

Comments

@eneajaho
Copy link
Contributor

Standalone api-s are becoming stable in v15, so it would be great if the components that we have can be converted to standalone.

@matschik matschik added the enhancement New feature or request label Nov 12, 2022
@psrebrny
Copy link

Hi, I would like to implement that option, but I'd like to know if it should be a simple change in current templates, or another option to choose an example (Angular standalone).

How should be done?

@eneajaho
Copy link
Contributor Author

I'd just change the current impl

@matschik matschik added content specific to `content` directory and removed enhancement New feature or request labels Feb 16, 2024
@matschik
Copy link
Owner

It's in progress in this PR I think: #245

@LcsGa
Copy link
Contributor

LcsGa commented Jul 30, 2024

That's not exactly what I did. I made another angular option called "Angular Renaissance" with every new feature from v14 to now, showing signals (with signal based components too), provideXxx functions, etc.
Right now, I have an issue when building the app. I haven't been able to fix it yet.

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

No branches or pull requests

4 participants