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

Tooling roadmap #173

Open
10 of 16 tasks
LPeter1997 opened this issue Jan 12, 2023 · 0 comments
Open
10 of 16 tasks

Tooling roadmap #173

LPeter1997 opened this issue Jan 12, 2023 · 0 comments
Labels
tooling Tooling related issues.

Comments

@LPeter1997
Copy link
Member

LPeter1997 commented Jan 12, 2023

  • See if the VS Project System can be integrated into and distributed sensibly. If so, we have free VS integration.
  • Add Visual Studio Language Server support (help)
  • Work out API documentation (compile & verify Draco source code in it for ex.)
  • Provide basic API documentation tooling
  • Add a REPL
  • Add a Notebook
  • Make the VS Code extension add build settings/config when recognizing a Draco project folder
  • Add a Debug Adapter (similar to the Language Server)
  • Make the VS Code extension suggest installing the Draco SDK, in case it's missing
  • Make the compiler write PDB files
  • Give the language server a CLI
  • Finish the SDK and Tooling packages, the SDK shipping the targets, the Tooling package shipping the compiler CLI and the language server CLI
  • Make the VS Code extension discover .NET on the machine (might be helpful tool)
  • Make the .NET tool be able to create a Draco projectfile
  • Make the VS Code extension automatically publishable from CI
  • Make the SDK and Tooling packages automatically publishable from CI
@LPeter1997 LPeter1997 added the tooling Tooling related issues. label Jan 12, 2023
@Binto86 Binto86 pinned this issue Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling Tooling related issues.
Projects
None yet
Development

No branches or pull requests

1 participant