Open niklas-wortmann opened 4 months ago
Describe the bug
Version: 22.0.0
I am doing code transformation with ts morph. Running sourceFile.insertVariableStatement(startLineNumber, {...} on code that uses semicolons returns vastly different results than running it on code without semicolons.
sourceFile.insertVariableStatement(startLineNumber, {...}
To Reproduce
The latest commit of this repository contains a failing test due to this issue. https://github.com/niklas-wortmann/nuxt/blob/useAsyncDataMigration/packages/nuxt/schematics/migrations/4_0_0/index.ts
running npm run test on this package json https://github.com/niklas-wortmann/nuxt/blob/useAsyncDataMigration/packages/nuxt/schematics/package.json will show the failing tests due to missing semicolons on the source file
npm run test
Expected behavior
Semicolons shouldn't have an impact here :D
Describe the bug
Version: 22.0.0
I am doing code transformation with ts morph. Running
sourceFile.insertVariableStatement(startLineNumber, {...}
on code that uses semicolons returns vastly different results than running it on code without semicolons.To Reproduce
The latest commit of this repository contains a failing test due to this issue. https://github.com/niklas-wortmann/nuxt/blob/useAsyncDataMigration/packages/nuxt/schematics/migrations/4_0_0/index.ts
running
npm run test
on this package json https://github.com/niklas-wortmann/nuxt/blob/useAsyncDataMigration/packages/nuxt/schematics/package.json will show the failing tests due to missing semicolons on the source fileExpected behavior
Semicolons shouldn't have an impact here :D