-
Notifications
You must be signed in to change notification settings - Fork 75
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 explicit way to create new file (a.k.a. wizard for new class/worksheet) #179
Comments
Thanks for suggesting this. I think it's a good idea. I'm moving this to the feature-requests repo, so that we can better prioritize our work. |
Ah, I think, there's no need for that, since I'm working on it, I just could not assign it to myself. |
@gabro I asked Aleksei to work on that, since the discoverability of worksheets is pretty poor at the moment. I think we can transfer it back to the repo. |
@gabro Sorry for not warning you about it! |
I think this is a good idea. I would avoid making this functionality limited to VS Code. It’s vest to implement most of the logic in the Metals server. We already have metals/inputBox that I believe is also supported in Vim. |
One VS Code api we don’t have an extension for right now is “quick open” (I think it’s called that). I’m not sure we need it for this feature however. We could add a server command “New Scala worksheet”. We might be able to expose this command in the context menu in VS Code but it should also be possible to invoke the command from other editors. |
Closed via #183 |
…rn/types/node-14.10.2 Bump @types/node from 14.10.1 to 14.10.2
The option to create new scala file or worksheet (or, potentially, notebook) should be added to
and, additionally can be added to
Should there be actual wizard?
Where wizard is a separate window with controls. It suppose something like IDEa's wizard to choose among Scala class/object/trait.
didOpen
, editor-independent.As a first iteration my suggestion is to create a simple explorer context menu addition under
New File
:The text was updated successfully, but these errors were encountered: