Skip to content

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

Merged
jplhomer merged 2 commits intov0.x-2022-10from
jl-fix-cli-js
Dec 16, 2022
Merged

Pass --no-typescript if the user didn't want typescript#342
jplhomer merged 2 commits intov0.x-2022-10from
jl-fix-cli-js

Conversation

@jplhomer
Copy link
Copy Markdown
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
Copy Markdown
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