You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I accidentally used the wrong casing for my state machine file (MyMachine.ts instead of myMachine.ts), and have since renamed it in git and vs code. (I used git mv to make sure git recognized the casing switch).
However, every time i save in the file, the xstate vscode extension changes the line:
tsTypes: {} as import('./myMachine.typegen').Typegen0
to tsTypes: {} as import('./MyMachine.typegen').Typegen0
I have tried renaming the machine file (e.g. to potato.ts) to change the typegen file, and then I renamed it back to the original name, but the typegen goes back to changing the file case. We also tried running xstate typegen, with the same behavior. Any suggestions?
Note: this does not occur on my teammates machines, which never had the wrong file casing.
The text was updated successfully, but these errors were encountered:
brmenchl
changed the title
vscode extension typegen doesn't respect file casing after rename.
xstate-cli typegen doesn't respect file casing after rename.
Oct 6, 2023
I accidentally used the wrong casing for my state machine file (
MyMachine.ts
instead ofmyMachine.ts
), and have since renamed it in git and vs code. (I usedgit mv
to make sure git recognized the casing switch).However, every time i save in the file, the xstate vscode extension changes the line:
tsTypes: {} as import('./myMachine.typegen').Typegen0
to
tsTypes: {} as import('./MyMachine.typegen').Typegen0
I have tried renaming the machine file (e.g. to
potato.ts
) to change the typegen file, and then I renamed it back to the original name, but the typegen goes back to changing the file case. We also tried runningxstate typegen
, with the same behavior. Any suggestions?Note: this does not occur on my teammates machines, which never had the wrong file casing.
The text was updated successfully, but these errors were encountered: