mdynnl
mdynnl
SSolidJS
Created by Liquido on 7/6/2024 in #support
How to store JSX element in a signal and render it from other elements
instead of directly passing dom nodes, you can pass a component then call it from other side.
6 replies
SSolidJS
Created by 𝔐𝔞𝔱𝔱𝔦𝔫 on 7/5/2024 in #support
Why is this not reactive? (using signal + html open attribute)
22 replies
SSolidJS
Created by 𝔐𝔞𝔱𝔱𝔦𝔫 on 7/5/2024 in #support
Why is this not reactive? (using signal + html open attribute)
why not e.preventDefault() + controls the open attribute by the signal?
22 replies
SSolidJS
Created by alexamy on 7/3/2024 in #support
Granular update of store array doesn't trigger effects depending on the whole array
to repeat, this thread's title is the whole point of solid and what solid is capable of.
23 replies
SSolidJS
Created by alexamy on 7/3/2024 in #support
Granular update of store array doesn't trigger effects depending on the whole array
this merging behavior can also be exploited to get the behavior op want
setStore('points', { [i]: { x: 0, y: 0 } })
setStore('points', { [i]: { x: 0, y: 0 } })
23 replies
SSolidJS
Created by alexamy on 7/3/2024 in #support
Granular update of store array doesn't trigger effects depending on the whole array
also there's no limitation on what get triggered from reactivity standpoint. it's just a choice made solely for performance.
23 replies
SSolidJS
Created by alexamy on 7/3/2024 in #support
Granular update of store array doesn't trigger effects depending on the whole array
this behavior of store merging top-level object properties surprises a lot of folks combined with the fact that solid playground's log has implicit deep tracking. both the old docs and new docs mention this but missing the other side of the whole story. we probably need an explainer of what gets triggered.
23 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
nope, i think it's just their build number, with that version mismatch, for some reason, doing v134 or even v1 loads correctly lol
11 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
would be cool to integrate https://generator.jspm.io/ with playground
11 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
11 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
too bad it's getting deprecated
11 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
the approach they took is less susceptible to these version mismatch issues
11 replies
SSolidJS
Created by halu on 6/27/2024 in #support
SOLVED: createLazyMemo Broken?
11 replies
SSolidJS
Created by enteleform on 6/16/2024 in #support
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
feel free to provide extra code, best if it can be copy/pasted to test 😆
39 replies
SSolidJS
Created by enteleform on 6/16/2024 in #support
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
or even this
import 'iconify-icon';

import type { IconifyIconProperties } from 'iconify-icon';
type BaseElementProps = JSX.IntrinsicElements['span'];
export interface IconifyIconProps
extends BaseElementProps,
IconifyIconProperties {
rotate?: string | number;
}

declare module 'solid-js' {
namespace JSX {
interface IntrinsicElements {
'iconify-icon': IconifyIconProps;
}
}
}

<iconify-icon width={20} icon="iconoir:pause-solid" />;
import 'iconify-icon';

import type { IconifyIconProperties } from 'iconify-icon';
type BaseElementProps = JSX.IntrinsicElements['span'];
export interface IconifyIconProps
extends BaseElementProps,
IconifyIconProperties {
rotate?: string | number;
}

declare module 'solid-js' {
namespace JSX {
interface IntrinsicElements {
'iconify-icon': IconifyIconProps;
}
}
}

<iconify-icon width={20} icon="iconoir:pause-solid" />;
39 replies
SSolidJS
Created by enteleform on 6/16/2024 in #support
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
also if you'd like to try
import 'iconify-icon';
import type { IconifyIconProperties } from 'iconify-icon';
type BaseElementProps = JSX.IntrinsicElements['span'];
export interface IconifyIconProps
extends BaseElementProps,
IconifyIconProperties {
rotate?: string | number;
}

export function Icon(props: IconifyIconProps) {
return (
// @ts-ignore
<iconify-icon {...props} />
);
}
import 'iconify-icon';
import type { IconifyIconProperties } from 'iconify-icon';
type BaseElementProps = JSX.IntrinsicElements['span'];
export interface IconifyIconProps
extends BaseElementProps,
IconifyIconProperties {
rotate?: string | number;
}

export function Icon(props: IconifyIconProps) {
return (
// @ts-ignore
<iconify-icon {...props} />
);
}
39 replies
SSolidJS
Created by enteleform on 6/16/2024 in #support
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
it's really weird this doesn't work
39 replies
SSolidJS
Created by enteleform on 6/16/2024 in #support
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
yeah, that would happen
39 replies
SSolidJS
Created by enteleform on 6/16/2024 in #support
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
could you try with directly call the icon component like Icon({ icon: playButton().icon })?
39 replies
SSolidJS
Created by enteleform on 6/16/2024 in #support
Broken reactivity @ `vite-plugin-solid` with `{dev:false}`, but works fine with `{dev:true}`.
interesting the attribute doesn't even update though
39 replies