Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Expose actions registry in IDE API #701

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

Merged
merged 1 commit into from
May 20, 2019
Merged

Expose actions registry in IDE API #701

merged 1 commit into from
May 20, 2019

Conversation

nhooyr
Copy link
Contributor

@nhooyr nhooyr commented May 20, 2019

No description provided.

@nhooyr nhooyr force-pushed the expose-keybind branch 2 times, most recently from f171819 to 1167833 Compare May 20, 2019 19:09
@nhooyr nhooyr changed the title Expose keybindings registry in IDE API Expose actions registry in IDE API May 20, 2019
@code-asher
Copy link
Member

We need SyncActionDescriptor exposed as well right?

@nhooyr
Copy link
Contributor Author

nhooyr commented May 20, 2019

@code-asher yea my bad, exposed.

@code-asher code-asher merged commit 0462a93 into master May 20, 2019
@@ -1,6 +1,9 @@
// tslint:disable no-any

import { ITerminalService } from "vs/workbench/contrib/terminal/common/terminal";
import { IWorkbenchActionRegistry } from 'vs/workbench/common/actions';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Importing from here won't work right?

It will within the project, but importing inside another would leave these unresolved.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure what you mean.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those files aren't included in the ide-api package so anything that imports it won't be able to resolve those types (only applies if you're using TypeScript of course). We'll want to fully encapsulate the API within the typings file before publishing a new version of the API.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not just use the vscode typings? Why are we wrapping?

Copy link
Member

@code-asher code-asher May 20, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'd have to include VS Code's code with the ide-api package. Since the files we import may import other files, it'd probably be easiest to just import all of VS Code, but it feels odd (to me) to include the entirety of VS Code just for the types.

The way VS Code does it is to have an entirely separate typings file like we're doing here and redefine all the types. Actually maybe we can just import their typings file and re-export some things from it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

@code-asher code-asher May 20, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually that wouldn't work because that doesn't include types for their internal methods, just what they expose to extensions.

@code-asher code-asher deleted the expose-keybind branch May 20, 2019 19:36
andreimc added a commit to devonlineco/code-server that referenced this pull request May 22, 2019
* upstream/master:
  Show hidden files by default
  Fix human readable byte size when zero
  Expose actions registry (coder#701)
  Set NODE_ENV and VERSION when building (coder#700)
  Don't try to create builtin extensions directory
  Suppress "disconnected" notification on extension host
  Extra extensions directories (coder#694)
  Updated Data Directory Flag (coder#664)
  Remove broken links (coder#671)
code-asher pushed a commit that referenced this pull request Jun 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants