Evgeniy OZ
Evgeniy OZ
I'm pretty sure about two things: 1. Modifying current `effect()` is too late. v18 is out, developers already use signals, and a lot of them use `effect()` (because most programmers...
Sorry, @garrettld, I don't see how your examples are related to modifying the state. In my understanding, the state is a set of variables, not some rendered image or DOM...
Hello! Great idea! Would be awesome to get in ngxtension too ;) It will really help with forms. Thanks a lot! #### 1. Just a clarification, in case I miss...
@markostanimirovic, we can't read the value of a signal without calling a function, and getters here are not a solution, because then we will not be able to bind a...
Perhaps some initial implementation would show us what is possible and what is not 👀
I agree it should emit the initial value, but it's too late to change. This change would create a devastating amount of breaking changes.
And it's released!
Their [installation guide for Angular](https://tailwindcss.com/docs/installation/framework-guides/angular) works fine, I was able to make it work in an Angular v19 app following that guide, even with plugins. It would be nice if...
100% agree. It is ridiculous that I have to use `outputFromObservable(toObservable(this.$v))`
So you think updating a model is an explicit action, and updating a signal is not? :)