# Introduction Adding integration test scaffold to the create twenty app and an example to the hello world app This PR also fixes all the sdk e2e tests in local ## `HELLO_WORLD` Removed the legacy implem in the `twenty-apps` folder, replacing it by an exhaustive app generation ## Next step Will in another PR add workflows for CI testing ## Open question - Should we still add vitest config and dep even if the user did not ask for the integration test example ? -> currently we don't - That's the perfect timing to identify if we're ok to handle seed workspace authentication with the known api key
31 lines
665 B
JSON
31 lines
665 B
JSON
{
|
|
"extends": "../../tsconfig.base.json",
|
|
"compilerOptions": {
|
|
"allowJs": false,
|
|
"esModuleInterop": false,
|
|
"allowSyntheticDefaultImports": true,
|
|
"strictNullChecks": true,
|
|
"alwaysStrict": true,
|
|
"noImplicitAny": true,
|
|
"strictBindCallApply": false,
|
|
"noEmit": true,
|
|
"types": ["jest", "node"],
|
|
"paths": {
|
|
"@/*": ["./src/*"],
|
|
"package.json": ["./package.json"]
|
|
},
|
|
"jsx": "react"
|
|
},
|
|
"include": [
|
|
"src/**/*.ts",
|
|
"src/**/*.tsx",
|
|
"src/**/*.d.ts",
|
|
"**/__mocks__/**/*",
|
|
"vite.config.ts",
|
|
"jest.config.mjs"
|
|
],
|
|
"exclude": [
|
|
"src/constants/base-application/vitest.config.ts"
|
|
]
|
|
}
|