This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
Terminal API: sending text to the newly created terminal doesn't work as expected #111
Assignees
Labels
kind/bug
Something isn't working
Comments
36 tasks
|
It's important for running the Kubernetes Tooling Che Plugin since a lot of the plugin's commands depend on these API calls. |
|
Added to the next sprint with High priority. Thank you for notifying. |
|
@AndrienkoAleksandr can we close this issue ? |
vinokurig
pushed a commit
that referenced
this issue
Apr 6, 2021
Copy plugins into 'v2/publisher' folders. Rename field name to displayName. Rename field id to name. Remove /meta.yaml from plugin links in index. Add deprecate section to old plugins. Rework scripts. Add migrate section to registry index. Add old notation plugins to v2 not to break exisiting workspaces. Adapt Readme.md. Signed-off-by: Oleksandr Garagatyi <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
window.createTerminalfollowed byterminal.sendTextleads to opening an empty terminal.Reproduction Steps
1/ Run the terminal-plugin sample in Che Theia
2/ Call the
Send text to the terminalcommand from the Command Palette.Expected behavior:
New Terminal is created and text is printed to the terminal
Note: it works as expected in standalone Theia
Actual behavior:
New Terminal is created but the text isn't printed to the terminal
The text was updated successfully, but these errors were encountered: