search

JordanMarr / fable-lit-fullstack-template

A SAFE-style template with Fable.Lit, Fable.Remoting and Giraffe
MIT License
58 stars 1 forks source link

Q: Fast components #10

Closed leolorenzoluis closed 1 year ago

leolorenzoluis commented 1 year ago

How's your experience with FAST components? It feels like it's buggy. Updating the value for a simple text-field does not update the next time but the correct value is set at runtime.

Edit: Looks like I just don't know what's the correct property to set. Changing value to .value does the trick.

leolorenzoluis commented 1 year ago

@JordanMarr Would like to know your reasoning why you have ShoeLace/FAST components though? Are there components in FAST that is just not enough or extensible as ShoeLace is?

JordanMarr commented 1 year ago

You don't have to use them if you don't want to. I just included them both as a starting point to demonstrate how to cherry pick components.

leolorenzoluis commented 1 year ago

Understood. I'll share my experience. It looks like the text input from FAST component has a slower debounce hence when I type fast the input shows correct value but when I pass use the other component it works fine, so just want to know if you experience any other weirdness with FAST components :)

JordanMarr commented 1 year ago

Ah I see. Yes, I had a large form with many Fluent UI (which is build on FAST) inputs until I started having strange issues/bugs with them. I think that might why I started looking around for a different library, which is when I switched to using Shoelace inputs.

The Shoelace team was also very helpful when I posted a question on their issues forum.

I would probably be using only Shoelace except for the fact that there are a few unique components in the Fluent UI framework that are really nice that don't exist in Shoelace, like the Slider, for example.