-
Notifications
You must be signed in to change notification settings - Fork 238
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
Support scaffolding scenario in vscode #5294
Conversation
All changed packages have been documented.
Show changes
|
You can try these changes here
|
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.
Suggestion to organize the source folder according to the feature:
Define a directory new
to store all the code for creating a typespec project,
in the future, there will be another directory emit
for code for emitting
packages/typespec-vscode/src/vscode-cmd/install-tsp-compiler.ts
Outdated
Show resolved
Hide resolved
Usually we will organize source in area with suitable granularity, not feature which can be big, small, without clear boundary and so on. For example, if we group by feature here, you will see lots of folders with only one file in it... |
Support scaffolding scenario in vscode whose user experience is like "tsp init". Vscode would collect information from end user and work with compiler to create new TypeSpec project underneath.
fixes: #4859