jer3m01 Comments - Answer Overflow

Topics

jer3m01

•Created by Puru on 2/22/2025 in #support

useDraggable how to make second argument reactive

You can just make position an accessor:

useDraggable(ref, [
  positionPlugin({current: position // no ()
  ...
]);

useDraggable(ref, [
  positionPlugin({current: position // no ()
  ...
]);

5 replies

•Created by Puru on 2/22/2025 in #support

useDraggable how to make second argument reactive

Because when you call position() it becomes a real value and not a signal anymore, since it's not in an effect it doesn't rerun

5 replies

•Created by Puru on 2/22/2025 in #support

useDraggable how to make second argument reactive

yeah it has to be an accessor or you have to wrap useDraggable in a createEffect user side

5 replies

•Created by Eatham on 11/9/2024 in #support

Jetbrains IntelliSense doesn't work

Also I recommend checking out https://docs.solidjs.com/reference/basic-reactivity/create-resource for doing your api request

5 replies

•Created by Eatham on 11/9/2024 in #support

Jetbrains IntelliSense doesn't work

Your IDE is correct, you should call the expression:

...
<div>
  Last User is {user()}
</div>
...

...
<div>
  Last User is {user()}
</div>
...

5 replies

•Created by agentsmith on 10/31/2024 in #support

Reactivity with shadcn-solid textfield

It also assures you're following the correct accessibility patterns

14 replies

•Created by agentsmith on 10/31/2024 in #support

Reactivity with shadcn-solid textfield

What are your issues with NumberField? It handles everything you've listed for you and much more.

14 replies

•Created by ensi on 9/8/2024 in #support

Hydration mismatch when trying to reference slot element outside of JSX

Also

const hasElementsOnAnySide = local.leadingElement || local.trailingElement; // not reactive

// should be:
const hasElementsOnAnySide = () => local.leadingElement || local.trailingElement;

const hasElementsOnAnySide = local.leadingElement || local.trailingElement; // not reactive

// should be:
const hasElementsOnAnySide = () => local.leadingElement || local.trailingElement;

25 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

yes

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

keyed makes the component rerun when the value changes

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

not sure if they're falsy

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

or a proxy maybe?

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

you return a getter instead

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

oh so you need it to work with falsy values?

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

You're probably able to make a generic helper function, something like maybeType(varname(), "number") => number | undefined

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

they should be avoided (but work, at least currently)

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

Yeah then a helper function like the one you made is needed

28 replies

•Created by Max on 9/6/2024 in #support

Possible to define more specific predicated for when prop on Match or Show

You can use anything as your condition, and you're not required to use the callback (but you lose typeguard) So you can have

<Match when={typeof varname() === "number"}>
  Number is {varname()} // however typescript doesn't understand type as number and thinks it might be undefined/null
</Match>

<Match when={typeof varname() === "number"}>
  Number is {varname()} // however typescript doesn't understand type as number and thinks it might be undefined/null
</Match>

28 replies

•Created by feras6169 on 9/5/2024 in #support

How do you recommend using SolidStart to access data for native mobile apps?

If you want to make both a website and an API for native then yes. Otherwise I wouldn't recommend, you won't end up using any of the features SolidStart provides and it will be weaker then API focused alternatives.

10 replies

•Created by Grahf on 9/2/2024 in #support

onChange only fires when press enter ?!

yep same as native onchange event, react has a custom behavior

8 replies