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

[vscode] Support SDK Generation for un-branded SDK from TypeSpec with major languages in VSCode Extension #5025

Open
2 tasks
lirenhe opened this issue Nov 8, 2024 · 3 comments
Assignees
Labels
ide Issues for VS, VSCode, Monaco, etc.

Comments

@lirenhe
Copy link
Member

lirenhe commented Nov 8, 2024

Clear and concise description of the problem

We need to support SDK Generation for un-branded SDK from TypeSpec for Java, .NET, Python, JS and GO in VSCode Extension

Tasks

Checklist

  • Follow our Code of Conduct
  • Read the docs.
  • Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
@lirenhe lirenhe added the ide Issues for VS, VSCode, Monaco, etc. label Nov 8, 2024
@RodgeFu
Copy link
Contributor

RodgeFu commented Nov 8, 2024

About the settings that end-user must configure before the codegen can work. It's better for us to have a way for IDE to figure them out instead of hardcoded. (i.e. if IDE finds the setting is required without default, we would consider it needs customer input? Or any better suggestions are welcome.)

@timotheeguerin
Copy link
Member

yeah we should try to keep the ide away from hard coding any libraries or emitters and count on the user config to figure out things and established compiler apis.

Would be good to understand what is actually wanted here? Running tsp compile . is the only thing needed and we have task for that already right @RodgeFu ?

@RodgeFu
Copy link
Contributor

RodgeFu commented Nov 12, 2024

this is to improve the end-to-end user experience when emitting common un-branded SDK code in vs code. Users should be able to generate code by using our selected common default emitters (i.e. C#) easily without checking command or related doc. Just some clicks in VS code should be all user needs to do. (And as the next step, user should be able to customize these emitters in the list through configuration as needed just like recommended extensions).

The POC below should be able to give you a brief idea about it (the emit part). Feel free to let us know if you have any suggestions on it. thanks.
https://microsoftapc-my.sharepoint.com/:v:/g/personal/wenjiefu_microsoft_com/Ecw5qN49uEdEsjKDe3PQ9IEBlsu_jHfjQ2HK-1QxbnVOgQ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ide Issues for VS, VSCode, Monaco, etc.
Projects
None yet
Development

No branches or pull requests

4 participants