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
With the new version standalone components are now the default. I think for some parts of our applications it makes sense to use these. Therefore I would suggest to migrate some components, pipes and directives as an example.
Also there is now a migration to transform constructor based injections to inject function calls. This improves extensibility of classes. Therefore I think we should do this change now.
There are some more transform schmatics regarding signals (we are currently not using them) which we should discuss if it makes sense to apply them with this update.
Ideally while doing the angular update the eslint version should be updated too as done here: f14929e.
TODO (non exhaustive):
Migrate some components, pipes, directives to standalone (can be done before the update)
There is a new angular version!
With the new version
standalone
components are now the default. I think for some parts of our applications it makes sense to use these. Therefore I would suggest to migrate some components, pipes and directives as an example.Also there is now a migration to transform constructor based injections to
inject
function calls. This improves extensibility of classes. Therefore I think we should do this change now.There are some more transform schmatics regarding signals (we are currently not using them) which we should discuss if it makes sense to apply them with this update.
Ideally while doing the angular update the eslint version should be updated too as done here: f14929e.
TODO (non exhaustive):
ngx-material-timepicker
with new Angular material timepicker https://material.angular.io/components/timepicker/overviewThe text was updated successfully, but these errors were encountered: