feat(cli): copy vscode ts settings#782
Conversation
🦋 Changeset detectedLatest commit: c16a939 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
4 Ignored Deployments
|
There was a problem hiding this comment.
The thought here is that maybe we will support other editors TS servers.
chanceaclark
force-pushed
the
feat/vscode-settings
branch
from
5d81216 to
2691afc
Compare
matthewvolk
left a comment
matthewvolk
left a comment
There was a problem hiding this comment.
Very nice! Originally I was thinking we should prompt and ask if they want the settings file created, but I like this way more, as it's extensible to other editors - and, there's probably never a reason they wouldn't want editor-specific config files created.
chanceaclark
force-pushed
the
feat/vscode-settings
branch
from
2691afc to
c16a939
Compare
⚡️🏠 Lighthouse reportLighthouse ran against https://catalyst-latest-p8nyj1i80-bigcommerce-platform.vercel.app 🖥️ DesktopWe ran Lighthouse against the changes on a desktop and produced this report. Here's the summary:
📱 MobileWe ran Lighthouse against the changes on a mobile and produced this report. Here's the summary:
|
3 participants
What/Why?
Creates the
.vscode/settings.jsonfile pointing to the Typescript SDK. This will help with new repos getting better TS support for gql-tada locally.Testing