-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add VSCode module to scaffolder #137
Conversation
98b6274
to
4cd643b
Compare
4cd643b
to
6a2ce8b
Compare
@@ -35,7 +35,7 @@ class ScaffoldParsedArgs(NamedTuple): | |||
name: Operation | |||
endpoints: list[Operation] | |||
template_type: Literal["basic", "openapi"] | |||
modules: list[Literal["database", "test"]] | None | |||
modules: list[str] | None |
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.
Is this change directly related to the VScode module? Do we lose anything by giving up the specificity of Literal["foo"]
?
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.
It is more related to the ability to create more Scaffold modules without having to update the modules
type or its values. We don't lose anything in practice; it has always been a list of strings, but now the specific values are unimportant to the type checker because they are dynamically set.
This PR adds a module to the scaffolder for users working with VSCode. Currently this just adds a launch.json with a couple debugger configurations.