Skip to content
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

Pass --no-typescript if the user didn't want typescript #342

Merged
merged 2 commits into from
Dec 16, 2022

Conversation

jplhomer
Copy link
Contributor

@jplhomer jplhomer commented Dec 16, 2022

Right now, we simply don't send --typescript if the user said they wanted the JS version of the template (in the temp init script), or if the user didn't pass the --typescript flag explicitly in the plugin/init script.

This changes behavior slightly for the official plugin, in that it defaults to JS unless TS was specified with the flag. I think this is what we've aligned on previously (cc @benjaminsehl) so it makes sense to encode that decision here, too. We could also add the "do you want to use typescript?" to the actual init command prompt, too.

Regardless, this solves the issue with the temp init script in the short term.

@github-actions

This comment has been minimized.

@jplhomer jplhomer merged commit 736e51f into v0.x-2022-10 Dec 16, 2022
@jplhomer jplhomer deleted the jl-fix-cli-js branch December 16, 2022 15:23
@benjaminsehl
Copy link
Member

Nice — “JS as default; but first class TS support” may be a good thing to add to the decision log

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.

3 participants