Piotr Stępniewski

@aitboudad We are not using NgModules anymore. We shifted to standalone APIs and build-in control flow. I think it's time to modernize also Formly.

I think v7 would be nice because compatibility problems of Angular v13. As standalone API's where introduced in Angular v14.

For example our teams application and things on top of Formly that we build are using standalone APIs. But we cannot do anything about Formly Core which is reason of...

In Angular v18 there will be even more breaking changes like new change observables for status, pristine, dirty etc. So it would be hard and super limiting to avoid introducing...

As suggested something like this last week on discord when talking with @rainerhahnekamp. It would be super useful to open many new capabilities and to avoid hacks with `Proxy` applied...

@ducin thats why I also proposed alternative name `withExplicit` **Edited:** Ahhh it was in other discussion

@Hulexis It prevent me to even setup storybook in my project and as it's just hobby project I can wait for proper release and fix. But thanks for sharing quick...

I tried to upgrade my library (https://github.com/k3nsei/ngx-signal-store-query) to latest version of Angular and TanstackQuery. Then this line stopped working https://github.com/k3nsei/ngx-signal-store-query/blob/08ea07f9c6e30259734b6ee6231be339a5d100c4/apps/demo/src/app/counter/counter.store.ts#L15 So the injection context is also missing in `injectMutation` which...

Using `inject` is not anty-pattern and clearly @arnoud-dv make big mistake there. DI is basic building block in Angular and almost everything there is based on that feature. Please see...

@BThomann then it would ruin all of our usage of TanStack Query and it becomes trash for us. Forcing us to move to `resource()` and `httpResource()`. Please look how `NgRx...