You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the Angular template (and generated source code) is still using @NgModule even though standalone components has been the recommended approach for a few years by now AFAIK. Template should be updated to use the now recommended approach.
Please note that we are using ABP Commercial with ABP Suite, but I would imagine this is the same for the free ABP as well. In fact, components generated by ABP Suite seem to use standalone components, so this might only be a "ABP Core" problem.
Thanks.
Version
0.9.23
User Interface
Angular
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Description
This is not a bug but rather an improvement.
It seems like the Angular template (and generated source code) is still using @NgModule even though standalone components has been the recommended approach for a few years by now AFAIK. Template should be updated to use the now recommended approach.
Please note that we are using ABP Commercial with ABP Suite, but I would imagine this is the same for the free ABP as well. In fact, components generated by ABP Suite seem to use standalone components, so this might only be a "ABP Core" problem.
Thanks.
Version
0.9.23
User Interface
Angular
The text was updated successfully, but these errors were encountered: