Soroosh Taefi comments

Results 67 comments of


                                            Soroosh Taefi

Form Binding (FirstNameComponent example) renders "undefined", crashes with nullable fields

#2713 fixed the crash issue, but still the problem of rendering the literal string `'undefined'` remains open.

hilla - autocrud: entities with mapped superclass not supported?

Hi @fer-marino, I'm not sure if I'm able to reproduce this issue. There are integration tests in the Hilla repository that shows this works: * Maven with Java entities: https://github.com/vaadin/hilla/tree/main/packages/java/tests/spring/react-grid-test...

hilla - autocrud: entities with mapped superclass not supported?

I think it will be very helpful if you could provide a minimal project or at least some code snippet with the exact method signatures for the endpoint and the...

Infinite project reloading

I cannot reproduce an **infinite** number of reloads/restarts on my machine: macOS 15.0.1, Vaadin 24.5.5, Java 21, Node v20.11.1, Vite v5.4.11 I tried the following combinations: * Creating a project...

feat(full-stack signals): make operations thenable

Also ListSignal's operations need another follow-up PR to enable the thenables, right?

Enable adding new validators by defining spring beans to complement the default Validator

I was mostly picturing it as looking up all the `Validator` beans, and validate parameters against all of them (including the default from Jakarta).

Enable fine-grained access control for full-stack signals

Apart from introducing new methods for the above mentioned operations, would it be OK if we just provide an extra `asReadonly()` method for the signals that adds all the necessary...

[Full-stack Signals] Add support for atomic arithmetic operation to NumberSignal

An overload of the `increment(delta: number = 1)` can support `add` and `subtract` operations as well. But, as using increment for `add` operation might be confusing, we can introduce also...

feat: add increment and add operations to NumberSignal

Closed in favor of #2694

[Full-stack Signals] allow client-side signal's default value to be set upon creation

In this case, do you see any caveats in implementing #2623 in a way that keeps `ValueSignal` abstract as it is and introduces `StringSignal` and `BooleanSignal`? Then, for implementing this...