question is: how you make vairance.(diff actions on one route, with diff params)

Tried to run it on windows and didn't work for me. rlyeh in kiruna on  ci ❯ go run .\cmd\dev\ 2024/08/24 18:30:09 Kiruna initializing sidecar refresh server on port 10000 2024/08/24 18:30:13 Kiruna Go binary compilation took: 3.9350176s 2024/08/24 18:30:13 Kiruna compilation complete: dist\bin\main 2024/08/24 18:30:13 Kiruna app started with pid 17316 2024/08/24 18:30:13 Kiruna error: failed to match file: syntax error in pattern 2024/08/24 18:30:13 Kiruna error: failed to match file: syntax error in pattern 2024/08/24 18:30:13 Kiruna using disk file system (development) Starting server on: localhost:8080 template: pattern matches no files: `index.go.html`

what are your thoughts on indie-stack

I misspoke at 6:12. It does a full refresh simply because the template needs to be reparsed after it’s edited.

Why did you pass the function? It would have worked better to use an event dispatcher. You could have created a use:action event on the component for when the event is dispatched.

Cool. Thanks.

This is great!

You have a very handy api. But why did you choose the snake_case style, since js uses camelCase everywhere?

Sorry to those of you who watched the old version with super low audio volume! Hopefully this one is much better.

UPDATE: An evolved version of this pattern has now been published to npm as an easily consumable toolkit: github.com/sjc5/remix-easy-mode#readme

This seems like a good pattern, I may use this on my app

Question: What would the advantages of this be compared to simply re-exporting the action from the api route, which i am currently doing?

Won’t passing the actual action to your custom hook force it to be bundled in the frontend code? Which would be you would include and other back end code in your front end like the prisma client for example? Would it be better to just pass the action type as a generic to the function?

Really cool, but wondering if there's a reason to choose this stack vs. just going with create-t3-app in the first place?

Opa, muito bom o vídeo, sobre a questão de ter um único id, poderia usar o sistema de bind:this do próprio svelte, para vincular cada botão, não?

I wanted to add something that worked for me. I modified the way you set id for each button with a random string function and created a random id "material-*randomString*" with length 8 and inside the button component. Thank you for this tutorial by the way

Thanks for making this video - helped a lot!

hey man, awsome video! Everything works fine, except i get an error from vscode: on "@use '@material....' " it tells me that it "can't find the stylesheet to import". Got any suggestions?

Thanks you very much 👌

Thanks :)

Thank you very much for the efforts that you put into the video. Learned a few things for sure. Excellent presentation skills as well. Cheers!

What about a complete svelte tutorial, I like the way you explain, thank you

Thank you! 😊

Thank you. I was looking into Svelte Material UI, but the documentation sucks. This way, at least I can understand what is going on