Mateusz Burzyński

I believe that this is being fixed by https://github.com/statelyai/xstate-tools/pull/229 since I've switched there to directly affect the given URI through a `WorkspaceEdit`: https://github.com/statelyai/xstate-tools/pull/229/files#diff-7fa1e063efd6c4eb2e3c9524b5ba5528fa926c78cdfa638c759312ebcffc40beR320-R321 . Previously we were first looking for...

I'm working on improving exactly this stuff. Thanks for raising the case of the forbidden transitions - it's an additional scenario I will keep in mind.

To fix this we should add support for `TemplateLiteral` here: https://github.com/statelyai/xstate-tools/blob/e938f4c7eed2b92bf480a03c2ec8458d9bdd95f9/packages/machine-extractor/src/actions.ts#L85-L100 We already have some logic to handle `TemplateLiteral`s (see the helper [here](https://github.com/statelyai/xstate-tools/blob/6736930525eb266343b7706c4aabb7b3dc65388c/packages/machine-extractor/src/scalars.ts#L72-L90)) but it's not used for the actions....

What does this solve? Where do you expect to see those extra keys?

I'm just slightly worried about the ripple effect of this change at the moment. I'm unsure how the previous thing was exactly utilized by our system. The current API of...

The breaking change I had in mind is about the shape of the extracted node - unfortunately, the AST shape leaks there. Now you have `.properties` property there, whereas previously...

This will get fixed next week since we are removing the dependency on Prettier from the VS Code extension.

We are both members of The Brick Gang 😉

We are removing the dependency on Prettier in [this PR](https://github.com/statelyai/xstate-tools/pull/229) so I believe that your issue is going to be fixed soon. Sorry for the delay!

> Another approach would be to generate the code without any indentation and let the project handle the indentation. Wouldn't this essentially lead to the same situation as the one...