-
-
Notifications
You must be signed in to change notification settings - Fork 35
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
feat(cli): check command #170
Conversation
🦋 Changeset detectedLatest commit: 105550e The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
77d4bc0
to
9b78ee6
Compare
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.
I don't think anything's strictly blocking the merge, assuming we'll keep iterating, so nothing here blocks this and we're good to go on the main implementation
const project = new Project({ | ||
tsConfigFilePath: './tsconfig.json', | ||
}); |
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.
Question (not a blocker): I'm a bit concerned about this being hardcoded to ./tsconfig.json
. And the same goes for other parts of the CLI using mainly ${CWD}/tsconfig.json
.
I tested new Project()
and it seems to indeed not trigger the resolver, so todo here to figure out resolver, which could be grouped with the polishing task to figure out reusing TsConfigResolver
from @ts-morph/common
, and then to also get to replacing resolveTypeScriptRootDir
with something externally maintained, as discussed 🤔 ❤️
3997f8b
to
575e5f7
Compare
575e5f7
to
105550e
Compare
Summary
Addresses part of #76
This adds
gql.tada check --severity error
which gets the current TS Project and runs the diagnostics from the LSP project