Will it be possible to nest a "hydrated" component inside a block that is "hydrate never"? I'm thinking of something similar to React Server Side Components, where the parent component is rendered only on the server and the child is hydrated.
In an template if check on multiple signals it is not currently possible to add multiple "; as" for each individual signal. Will this functionality be added?
@if (signal1(); as signal1 && signal2(); as signal2)
Won't the full introduction of a new "standalone" API and zoneless applications make Angular less opinionated and make it harder for developers to choose the right implementation solutions?
Is there any plan to make Angular CLI more extensible in terms of allowing community and custom update recipes, similar to how NX enables migration recipes with migration.json? It would be great if Angular could support community-driven or custom migration scripts to ease the process of updating complex applications and allow for more tailored upgrades.
Is the new ngrx signal store events compatible with the Redux DevTools, and are there any tip and tricks how you can debug store changes on the new signal store?
What would an HTTP client without RxJS look like? Will a new HTTP client be offered as a secondary entry point, or will the current HTTP client be extended or adapted?
You recommended to push data fetching up to the router level. What is the recommended way of indicating loading state for user, if component needs a lot of data to be loaded (i. e. for router navigation to finish)?
In the keynote it was mentioned that the signal schematic can migrate ~90% of input/output to signals. What happens with the 10% that it can’t figure out? Marked with a comment?
For google cloud console,
Instead of splitting the monolith into a lot of apps, had you considered the monorepo approach with (distributed) computational caching (like nx)?
For Google cloud console, does it use some mechanism to share code between the microfrontends or does every microfrontends have their own copy of Angular for example?
Do you think it’s better to call directly your micro services backend APIs creating a lot of small http requests, or trying to aggregate everything ( in a BFF or Graphql server…) , to limit http requests?
New hydration functionallity supports loading js for components on idle. Is something similar possible for lazy loaded component in the application routes? (i. e. eagarly loading code for another routes, when network is idle)
If you had a magic wand, is there any legacy web API that you would change? Maybe there is some quirky JS behavior that stops you from implementing some idea in Angular?
You put a lot of effort in making new mechanisms backwards compatible - why don’t you create Angular 3, the zoneless, incremental hydration enabled killer framework instead?
Hey, I am just working on a brand new angular app using m3. As you said and know I am one of those people struggling with getting theming to do what I want. I am very curios about the changes to theming api that you talked about. How easy will it be to migrate existing code using m3 theming from "old api" to the new one?
In a topic with partial hydration was mentioned - measure. So, how much do we win in time and sizes in the site example? Probably it's better to describe in percentages
Google Cloud Console uses custom solution based on iframes to manage huge (biggest in the world) Angular app. What could be official Angular provided/suggested solution to split such applications today and in upcoming future?
When we start building a new Angular application now, which testing framework should we use? Still karma/jasmine or already jest/vitest? What would be the most future proof solution?
The idea behind standalone components was to simplify the api. As a side affect writing unit tests became more complex adding more boilerplate code with overrideComponent. Was is the future of Testbed?
What’s the point of using withHooks() in signal store if you can simply call methods from corresponding component lifecycle hooks? Isn’t it unnecessary duplication?
To Lukacz Jancrvicz: how did you come up with the exact way to split the monolith into microfrontends? What was your approach and did you use a particular arch. pattern (DDD for example)?
The new ESM based Angular build is still "missing" some of the features of the old webpack build like the webpack magic comments. This would be even more helpful as the new build generates way more chunks. Having custom chunk names, like it was possible in the webpack build by defining a chunk name at the dynamic import, would be really helpful. Is such a feature planned for the new build?
Hi from angular 14 user! (don't blame me =) )
You've introduced signals for http calls. Does it mean angular team in general switch their vision to make calls directly from components instead of services? In other words, are we are going away from MVC pattern?
Will futher versions of angular material provide complex components like multiselect with autocomplete and lazy loading elements from API when HttpResource will be implemented?
We are having problems with our Angular Apps using new ESM based build, Service worker and SSR. We use SwUpdate to trigger a full reload when the app has an update or becomes unrecoverable. Still, our customers report 404 errors on chunks, which can only be fixed by doing a hard reload manually. In the web, we cannot find a lot about this problem. In our apps it happens some times, but not reproducable consistently.
how does the output html will look like when using selectorless components? Doesn't it makes Angular "incompatible" with web components idea?