-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for @tsconfig/ember 3.0.0 #614
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -94,7 +94,7 @@ module('create', function () { | |
// @ts-expect-error violate types to check if it fails in weakly-typed envs | ||
create(''); | ||
assert.true(false, 'should error'); | ||
} catch (e) { | ||
} catch (e: any) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can we have There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can't use the type
This is an annoying issue with TypeScript, see a long discussion thread here. Alternatively, and probably more correct, we can type this as |
||
assert.strictEqual(e.message, 'Definition can not be a string'); | ||
} | ||
}); | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,47 +1,18 @@ | ||
{ | ||
"extends": "@tsconfig/ember/tsconfig.json", | ||
"compilerOptions": { | ||
"target": "es2020", | ||
"allowJs": true, | ||
"moduleResolution": "node", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd like to make sure we still support the Maybe a better way to test would be just to create a new cutting-edge test app, with just a single dummy test that imports some ...Or, alternatively, we could create a "legacy" test app with that dummy test + Thoughts? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
"allowSyntheticDefaultImports": false, | ||
"noImplicitAny": true, | ||
"noImplicitThis": true, | ||
"alwaysStrict": true, | ||
"strictNullChecks": true, | ||
"strictPropertyInitialization": true, | ||
"noFallthroughCasesInSwitch": true, | ||
"noUnusedLocals": true, | ||
"noUnusedParameters": true, | ||
"noImplicitReturns": true, | ||
"noEmitOnError": true, | ||
"noEmit": true, | ||
"inlineSourceMap": true, | ||
"inlineSources": true, | ||
// The combination of `baseUrl` with `paths` allows Ember's classic package | ||
// layout, which is not resolvable with the Node resolution algorithm, to | ||
// work with TypeScript. | ||
"baseUrl": ".", | ||
"module": "es6", | ||
"experimentalDecorators": true, | ||
"paths": { | ||
"test-app/tests/*": [ | ||
"tests/*" | ||
], | ||
"test-app/*": [ | ||
"app/*" | ||
], | ||
"ember-cli-page-object": [ | ||
"addon" | ||
], | ||
"ember-cli-page-object/*": [ | ||
"addon/*" | ||
], | ||
"ember-cli-page-object/test-support": [ | ||
"addon-test-support" | ||
], | ||
"ember-cli-page-object/test-support/*": [ | ||
"addon-test-support/*" | ||
], | ||
"*": [ | ||
"types/*" | ||
] | ||
"test-app/tests/*": ["tests/*"], | ||
"test-app/*": ["app/*"], | ||
"ember-cli-page-object": ["addon"], | ||
"ember-cli-page-object/*": ["addon/*"], | ||
"ember-cli-page-object/test-support": ["addon-test-support"], | ||
"ember-cli-page-object/test-support/*": ["addon-test-support/*"], | ||
"*": ["types/*"] | ||
} | ||
}, | ||
"include": [ | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like we should remove this from the package.json or from the ember-try scenario. I tend to remove it from the
package.json
in scope of the currenttest-app
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment above.