Skip to content

Rework some of the project setup #317

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

Merged
merged 1 commit into from
Apr 23, 2021
Merged

Conversation

adamthom-amzn
Copy link
Contributor

This makes it much friendlier with IDEs, both in terms of finding jest symbols
and running tests from within the IDE. tsconfig.cjs.json is not what a
TypeScript language service looks for by default, and we aren't bailed out by
its presence in a parent workspace since these are standalone libraries.

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This makes it much friendlier with IDEs, both in terms of finding jest symbols
and running tests from within the IDE. tsconfig.cjs.json is not what a
TypeScript language service looks for by default, and we aren't bailed out by
its presence in a parent workspace since these are standalone libraries.
@adamthom-amzn adamthom-amzn merged commit ad01f42 into smithy-lang:ssdk Apr 23, 2021
JordonPhillips pushed a commit to JordonPhillips/smithy-typescript that referenced this pull request Apr 26, 2021
This makes it much friendlier with IDEs, both in terms of finding jest symbols
and running tests from within the IDE. tsconfig.cjs.json is not what a
TypeScript language service looks for by default, and we aren't bailed out by
its presence in a parent workspace since these are standalone libraries.
srchase pushed a commit to srchase/smithy-typescript that referenced this pull request Mar 17, 2023
This makes it much friendlier with IDEs, both in terms of finding jest symbols
and running tests from within the IDE. tsconfig.cjs.json is not what a
TypeScript language service looks for by default, and we aren't bailed out by
its presence in a parent workspace since these are standalone libraries.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants