Independently building at night
- Flotes · Markdown Note-taking Built for Learning
- Tomatillo Timer · Study timer that syncs to music
- Better Commits · CLI to make conventional commits
Definitely looking to switch back to a custom setup when I get the chance!
Definitely looking to switch back to a custom setup when I get the chance!
Svelte-Language-Server 0.17.19
I'm also using LazyVim with the Svelte LazyExtra. This is actually a whole other issue. Without it, changing TS files does not reflect changes in Svelte files. With it, big svelte projects crash the ls. 😭
My svelte lsp setup: github.com/Everduin94/d...
Svelte-Language-Server 0.17.19
I'm also using LazyVim with the Svelte LazyExtra. This is actually a whole other issue. Without it, changing TS files does not reflect changes in Svelte files. With it, big svelte projects crash the ls. 😭
My svelte lsp setup: github.com/Everduin94/d...
Too many ideas, not enough time 😅
Too many ideas, not enough time 😅
I definitely don't some stuff you have like didChangeWatchedFiles = false in my config
I will give that a try when I get the chance!
I definitely don't some stuff you have like didChangeWatchedFiles = false in my config
I will give that a try when I get the chance!
client:notify instead of client.notify
So confusing 🫤. - There are examples of this workaround everywhere. They all use client.notify. Only example I've seen using client:notify was a Neovim 12 user, I'm on 11.
client:notify instead of client.notify
So confusing 🫤. - There are examples of this workaround everywhere. They all use client.notify. Only example I've seen using client:notify was a Neovim 12 user, I'm on 11.
For context I'm on Neovim v0.11.3
For context I'm on Neovim v0.11.3
(4/4)
(4/4)
time and intervals don't really map on to FSM. They technically just have 1 "state".
(3/4)
time and intervals don't really map on to FSM. They technically just have 1 "state".
(3/4)
It has many different states that affect each other:
- running / idle
- study, short-break, long-break,
- current-time / max-time
- current-interval / max-interval
(2/4)
It has many different states that affect each other:
- running / idle
- study, short-break, long-break,
- current-time / max-time
- current-interval / max-interval
(2/4)
I've been using Runed FSM more and more this afternoon and what I think I am really looking for is more-so something like: X-State's "Context" stately.ai/docs/context
My use case... (1/4)
I've been using Runed FSM more and more this afternoon and what I think I am really looking for is more-so something like: X-State's "Context" stately.ai/docs/context
My use case... (1/4)
Also to clarify. Nesting might be one way of solving my problem. Alternatively, if it makes sense to compose multiple state machines, that would probably work as well. - I'm not sure what is the standard way of handling states within states.
Also to clarify. Nesting might be one way of solving my problem. Alternatively, if it makes sense to compose multiple state machines, that would probably work as well. - I'm not sure what is the standard way of handling states within states.
A package would be nice for the sk version, but I like how obvious it makes everything. On a subject that normally feels very magical (imo 🙂).
A package would be nice for the sk version, but I like how obvious it makes everything. On a subject that normally feels very magical (imo 🙂).
svelte.dev/docs/kit/ser...
I have used workbox, vite-pwa, etc... and this is so much simpler and works so much better (for me), that I will link it anytime I get the chance 😅
svelte.dev/docs/kit/ser...
I have used workbox, vite-pwa, etc... and this is so much simpler and works so much better (for me), that I will link it anytime I get the chance 😅
Disabled, of course, removes the active state . Thus, closes the dropdown immediately. 🫠
Disabled, of course, removes the active state . Thus, closes the dropdown immediately. 🫠
My dropdown is pure CSS, opens based on the button or it's children being the active element.
I would click a button, the dropdown would close immediately. Even though that button is a child of the dropdown.
(1/2)
My dropdown is pure CSS, opens based on the button or it's children being the active element.
I would click a button, the dropdown would close immediately. Even though that button is a child of the dropdown.
(1/2)