When can we expect Angular Resources to move from the 'experimental' status to 'developer preview'? Additionally, is there a timeline for when guidance will be available on using Resources for POST requests (server-side mutations)?
When can we expect Angular Resources to move from the 'experimental' status to 'developer preview'? Additionally, is there a timeline for when guidance will be available on using Resources for POST requests (server-side mutations)?
Can we dynamically create signal stores, form stores, and validation schemas at run time based on metadata (required, read-only, etc.) for each field defined on the backend?
New architecture looks like completely new framework. Is it better than React? If I need to learn everything from scratch, isn’t it better to learn React instead, which has broader market share and more positions to apply for job?
Hello, have already started using the NgRx signal store implementation for new features, on the other hand, I have a lot of old NgRx store implementations. Is there any documentation or playgrounds to facilitate migration to signal store? Thanks.
Hello, first of all, I would like to thank you for these presentations. It's incredible to see Angular develop. My question is: why is the signal effect (() => ...) not recommended for use and what are its side effects? Thank you.
Can we expect future Resource integration with Router Resolvers, making the resolved data available inside the component as well - for example, to trigger a reload?
Shall we use signal events or not? Some people say it's just a fallback to classic store and that's conceptually different than signal graph pattern. Personally I enjoy the redux pattern and it's separation of command from the whatever going to happen.
Would it be possible for resources to be “enabled” only when certain conditions are met? For example when 2 signals contain value. (Similar to tanstack query’s enabled property)