gsoutz Comments - Answer Overflow

Topics

gsoutz

•Created by gsoutz on 3/18/2025 in #support

How to test for is loaded for a create async source change

cursor path is always set to some value anyway, and it is saved in database. It's just shouldn't be set to a wrong path if the replay_tree is the old one. I am fully aware and familiar how async await or promises work. It's just tracking the control flow of these effects, which I have to use in order to build something functional with solid.js is getting worse.

10 replies

•Created by gsoutz on 3/18/2025 in #support

How to test for is loaded for a create async source change

I set a state variable is_replay_tree_just_loaded, set to false initially and set to true on this then clause of the async query to get the replay_tree. so I can test against that to see if replay_tree is just loaded to be available for display. I also do a state transition to a next state where tree is ready to be used. I tried both setTimeout and queueMicrotask, queueMicrotask, is too early to trigger replay_tree_is_just_loaded before the replay_tree is actually has the fresh value, so it throws in my code because code uses old replay_tree . setTimeout however seemed to fix the issues. However I am so troubled doing these things with so many caveats and hard to track down state flow. I am not sure if it's the nature of solid.js or nature of using async data loading logic.

10 replies

•Created by gsoutz on 3/18/2025 in #support

How to test for is loaded for a create async source change

the cursor is also a property in the replay tree, like this is what resolves inside a store, like get articles() { property getter inside the store.

let default_replay_tree = { flat_nodes: [], cursor_path: '' } etc.

let default_replay_tree = { flat_nodes: [], cursor_path: '' } etc.

10 replies

•Created by gsoutz on 3/18/2025 in #support

How to test for is loaded for a create async source change

Promise resolves a replay tree, when the replay tree is loaded, I want to set the cursor to a specific location, so it renders the correct path in the tree. As a solution I could tell to load the replay tree with the cursor set to correct location, but I just had to ask before I do that.

10 replies

•Created by gsoutz on 3/18/2025 in #support

Why is this store change doesn't trigger a reactive computation

ok thank you i will restructure based on that new insight.

11 replies

•Created by gsoutz on 3/18/2025 in #support

Why is this store change doesn't trigger a reactive computation

oh because of optimizations, i see

11 replies

•Created by gsoutz on 3/18/2025 in #support

Why is this store change doesn't trigger a reactive computation

I don't understand, this set state call

     set({ state: 'select-next' });

     set({ state: 'select-next' });

changes the state.current reference to a new object.

11 replies

•Created by gsoutz on 3/15/2025 in #support

can't setup a basic state machine interactive quiz type of game

full code is here https://github.com/eguneys/aidchess24/blob/rework/src/views/repetition/Show.tsx

11 replies

•Created by gsoutz on 3/15/2025 in #support

can't setup a basic state machine interactive quiz type of game

    type StateBoot = { state: 'boot', next: undefined }
    type StateLoadList = { state: 'load-list', next: undefined }
    type StateListNoItem = { state: 'list-no-item' }
    type StateSelectNext = { state: 'select-next', next?: ModelRepeatDueMove }
    type StateLoadNext = { state: 'load-next', next: ModelRepeatDueMove, is_previous_attempt: boolean }
    type StateLoadedPreview = { state: 'loaded-preview', next: ModelRepeatDueMove, is_previous_attempt: boolean }
    type StateLoadedIdle = { state: 'loaded-idle', next: ModelRepeatDueMove, show_previous_moves: boolean, is_previous_attempt: boolean }
    type StateAttemptResult = { state: 'attempt-result', next: ModelRepeatDueMove, attempt_result: RepeatAttemptResult, is_previous_attempt: boolean }
    type StateAutoGoNext = { state: 'auto-go-next', next: ModelRepeatDueMove, is_previous_attempt: boolean }

    const is_boot = (state: SomeState): state is StateBoot => state.state === 'boot'
    const is_load_list = (state: SomeState): state is StateLoadList => state.state === 'load-list'
    const is_list_no_item = (state: SomeState): state is StateListNoItem => state.state === 'list-no-item'



    type SomeState = StateBoot | StateLoadList | StateListNoItem

    const [state, set_state] = createStore<StoreState>({
        current_state: { state: 'boot', next: undefined }
    })

    createEffect(() => {
        if (is_boot(state.current_state)) {
            set_current_state({
                state: 'load-list',
                next: undefined
            })
        }
    })

    type StateBoot = { state: 'boot', next: undefined }
    type StateLoadList = { state: 'load-list', next: undefined }
    type StateListNoItem = { state: 'list-no-item' }
    type StateSelectNext = { state: 'select-next', next?: ModelRepeatDueMove }
    type StateLoadNext = { state: 'load-next', next: ModelRepeatDueMove, is_previous_attempt: boolean }
    type StateLoadedPreview = { state: 'loaded-preview', next: ModelRepeatDueMove, is_previous_attempt: boolean }
    type StateLoadedIdle = { state: 'loaded-idle', next: ModelRepeatDueMove, show_previous_moves: boolean, is_previous_attempt: boolean }
    type StateAttemptResult = { state: 'attempt-result', next: ModelRepeatDueMove, attempt_result: RepeatAttemptResult, is_previous_attempt: boolean }
    type StateAutoGoNext = { state: 'auto-go-next', next: ModelRepeatDueMove, is_previous_attempt: boolean }

    const is_boot = (state: SomeState): state is StateBoot => state.state === 'boot'
    const is_load_list = (state: SomeState): state is StateLoadList => state.state === 'load-list'
    const is_list_no_item = (state: SomeState): state is StateListNoItem => state.state === 'list-no-item'



    type SomeState = StateBoot | StateLoadList | StateListNoItem

    const [state, set_state] = createStore<StoreState>({
        current_state: { state: 'boot', next: undefined }
    })

    createEffect(() => {
        if (is_boot(state.current_state)) {
            set_current_state({
                state: 'load-list',
                next: undefined
            })
        }
    })

11 replies

•Created by gsoutz on 3/15/2025 in #support

can't setup a basic state machine interactive quiz type of game

Here's an example code showcasing how I achieved my success with this feature: So this kind of system basically works with no bugs at least visually as far as I could test it under 1 hour.

11 replies

•Created by gsoutz on 3/15/2025 in #support

can't setup a basic state machine interactive quiz type of game

I managed to track down a couple of re calculations happening , but one change leads to another and I end up in unstable state again.

11 replies

•Created by gsoutz on 3/14/2025 in #support

I need to run an effect when an async signal or a store signal, or another async signal are equal

there is 2 separate async data is loading, and they are changing over time, i want to display the view only when both data are loaded and in sync.

8 replies

•Created by gsoutz on 3/10/2025 in #support

query function invalidates the cache every 10 clicks

I completely understand your very detailed explanation. I think I have to keep a reference to the fetch results somewhere basically invent my own caching mechanism. Although It's not a main concern to me right now, since my app is all working local first.

34 replies

•Created by gsoutz on 3/10/2025 in #support

query function invalidates the cache every 10 clicks

But I don't have the list of id's 1 and 2 before hand to hardcode them like that. I don't see how this is useful to me. I just copied the example code from the real-world project. If you have a recent code repository on how to work out a real world example that would be great. https://github.com/solidjs/solid-realworld

34 replies

•Created by gsoutz on 3/10/2025 in #support

query function invalidates the cache every 10 clicks

I don't understand what you guys are talking about. Also your example is acting weird, not sure how it is supposed to work, but. Sometimes the Result: time value updates sometimes it doesn't update, each time I reload the example. and it never hit's the database again.

34 replies

•Created by gsoutz on 3/10/2025 in #support

query function invalidates the cache every 10 clicks

ok thank you very much.

34 replies

•Created by gsoutz on 3/10/2025 in #support

query function invalidates the cache every 10 clicks

can you elaborate what is happening with your suggestion because I don't understand.

34 replies

•Created by gsoutz on 3/10/2025 in #support

query function invalidates the cache every 10 clicks

oh ok thank you. Maybe mention that very important detail in the docs, and suggest an alternative, I used to use "cache" but the docs already says the use query instead. So what is the purpose of revalidate then if no long lived cache exists.

34 replies

•Created by gsoutz on 3/7/2025 in #support

What to do instead of loading a model with createMemo inside a createResource computation

As in data separate from behaviour. It was never meant to create "reactive objects"

I did some research, and stumbled upon this: https://github.com/solidjs/solid-realworld/blob/main/src/store/createAuth.js What is the difference between this code and my code. What is wrong with putting setters and getters inside the same "array" or an "object".

7 replies

•Created by gsoutz on 3/7/2025 in #support

What to do instead of loading a model with createMemo inside a createResource computation

Here I created a playground, but I don't understand it is not giving the warning here. https://playground.solidjs.com/anonymous/958d99b1-8bf7-4e99-9918-19d396435658

7 replies