Skip to content
This repository has been archived by the owner on Feb 25, 2024. It is now read-only.

VS Code Extension mangles machine code #386

Open
EightArmCode opened this issue Sep 30, 2022 · 1 comment
Open

VS Code Extension mangles machine code #386

EightArmCode opened this issue Sep 30, 2022 · 1 comment

Comments

@EightArmCode
Copy link

Description

I'm not sure where to report this. I am guessing this is a prettier/eslint conflict. I just added eslint-config-xstate today - is it possible that it conflicts with this? I also have a prettier/eslint config of my own that's all about business. What I DO know is that I opened the visualizer today and it behaved very strangely. The screen flickered, and it ate half my machine code, messing up the formatting, etc. It also did not stop. It appeared to be caught in a formatting loop, but like I said, just guessing.

Expected Result

Visualizer will chart my state machine without deleting half the code, etc

Actual Result

Visualizer mangled my machine code. (Don't worry, I use VCS)

Reproduction

Not sure how to do that

Additional context

That's all. I would just like to use the local visulaizer, but cannot.

@Andarist
Copy link
Member

I'm working on the improvements to the code<->Studio syncing so hopefully that should resolve it. I'm not aware of any formatting loop though - more info about this would be appreciated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants