Mateusz Burzyński
Mateusz Burzyński
Right - it would be nice though if this particular library would do this automatically for me.
@SimenB do you think the fuzzy algorithm should become the default? My personal take on this would be that - yes, it would be great as a default. Not sure...
I know that it has been a while since you have created this PR - but could you rebase this on top of the main branch and add snapshots tests...
Yeah, this is what I had in mind - thank you 🙏 I'm gonna try to take a look at this soon
The most likely culprit is the fact that the code lens command embeds the possibly outdated arguments: https://github.com/statelyai/xstate-tools/blob/53ba81ba15f991952f220c0b519225328f06b9f4/apps/extension/server/src/server.ts#L164-L173 The fix would be to limit the arguments and grab the config...
This is being superseded by https://github.com/statelyai/xstate-tools/pull/208
We are aware of the issue and we are working on improvements in this part of the code to remedy this.
I don't think so - but we are overhauling the implementation and we'll try to remove any possibility of this happening.
The reported issue is somewhat vague and contains a bigger machine that requires some analysis. Could you focus on the problematic pattern and clearly state the actual & expected results?
Implementation notes: 1. we could remove `@xstate/tools-shared` and move its code to `@xstate/cli`. The extension could just import from it directly (it would be bundled into the extension's code) but...