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

Generated template for custom notebook renderers won't compile #125196

Closed
andreamah opened this issue Jun 1, 2021 · 10 comments
Closed

Generated template for custom notebook renderers won't compile #125196

andreamah opened this issue Jun 1, 2021 · 10 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@andreamah
Copy link
Contributor

Testing #125016

When I generate the template extension code using npm install -g generator-code && yo code --insiders, I get an error in client/index.ts
image

@andreamah andreamah added the bug Issue identified by VS Code Team member as probable bug label Jun 1, 2021
@andreamah
Copy link
Contributor Author

Following up on this, there are also some issues with extension/sampleProvider.ts when I download the template including the kernel.
image

@connor4312
Copy link
Member

thanks, looks like several updatees are needed. I recommend using the github-issues-notebook as a sample/starter for verification purposes

@jrieken
Copy link
Member

jrieken commented Jun 7, 2021

@tanhakabir Where do those template come from?

@tanhakabir
Copy link
Contributor

generator-code, I haven't pushed an update for the serializer/kernel yet since we'll be pushing the API onto stable soon, but the renderer should work. I can check

@jrieken jrieken removed their assignment Jun 16, 2021
@connor4312
Copy link
Member

@tanhakabir I think you resolved this with the onboarding work last iteration?

@connor4312
Copy link
Member

Looks like it microsoft/vscode-generator-code@4da9eda

@connor4312 connor4312 added this to the July 2021 milestone Jul 7, 2021
@isidorn isidorn added verified Verification succeeded and removed verified Verification succeeded labels Jul 29, 2021
@TylerLeonhardt
Copy link
Member

Looks fixed:

image

One question... I noticed that it has a main entry point. This isn't needed right? This also blocks the generated extension to be installed on Web because of that main entry point without a browser one.

I think we probably want to either remove the main or add a browser.

@TylerLeonhardt TylerLeonhardt added the verified Verification succeeded label Jul 29, 2021
@connor4312
Copy link
Member

@TylerLeonhardt I think that's a good idea, the trouble is that if the user doesn't have a notebook capable of outputting the given mimetype already then they can't see their renderer. I know we're talking about having a built-in ipynb deserializer, though it looks like that doesn't exist yet. @rebornix is that still the plan? If so we can include a sample.ipynb and know that it'll work.

@rebornix
Copy link
Member

rebornix commented Aug 2, 2021

I know we're talking about having a built-in ipynb deserializer, though it looks like that doesn't exist yet. @rebornix is that still the plan? If so we can include a sample.ipynb and know that it'll work.

We have the ipynb serialzier shipped with the coming VS Code Stable.

@connor4312
Copy link
Member

Oh, sweet! I see it now, I was a couple Insiders behind on my home PC.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

7 participants