Thanks for the link!

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!

This is the fix for me.

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.

Outside of the Svelte LazyVim Extra, this used to work for me, but that's no longer the case.

For context I'm on Neovim v0.11.3

Also just wanted to add, I'm really enjoying using FSM, thanks for your effort on it! - This isn't so much a request as it is just me thinking out-loud 😅. I could copy FSM, try to add context myself, and see if it makes sense. Or maybe I'm just complicating things for the sake of consistency 😆

I think with something like context, I could use FSM to represent time and interval. - Since it only has 1 state, the benefit is just associating that data/state with its actions in an API that matches the rest of my code that's using FSM.

(4/4)

I got this working using 2 instances of FSM for running/idle and study/break. - So I don't necessarily need nesting here, this works fine and make sense to me.

time and intervals don't really map on to FSM. They technically just have 1 "state".

(3/4)

I am re-writing portions of a timer application.

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)

Hey thanks for taking the time to reply.

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)

Thanks for the tag!

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.

Yes, Svelte is the Sung Jin-woo of web development.

I could never get offline to work quite right with workbox/vite-pwa and had a lot of issues when developing. Skill issue on my part 😅.

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 🙂).

Maybe not helpful since I see you mentioned React Native. But, if you do happen to be using Svelte-Kit, it's this.

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 😅

Reminds me of this: www.reddit.com/r/neovim/com...

24k lines of code all written on a phone 😅

I was setting the clicked button (the now active child element) to disabled, during the server-side cookie update.

Disabled, of course, removes the active state . Thus, closes the dropdown immediately. 🫠

Also, ran into a bug working on this that makes total sense but had me so stumped.

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)

Good question :). This is a rewrite so hypothetically:

I was considering each settings tab represented by a JSON column on a Postgres Table. - In that context, submit the whole page every time.

Otherwise, totally granular, each field is a column on the BE.

First attempt 👀

Had a few hiccups where it seemed like the highlight group was off (like `new` is an Operator). Or getting the catch block parameter to match a function parameter.

Still not totally convinced on nothing to signify built-ins / keywords 😅.

😅 Yeah haha. I feel some of it's "batteries" are what holds it back nowadays.

Things like HttpClient (rxjs), Dependency Injection everything, etc... feel like overhead compared to the other frameworks today.