You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I bring up "Runtime Status", I see the below 2 messages relating to the 'proposed api' usage for diff/merge view.
I'm filing this issue to see what team thinks about this, do we want to keep the messages displayed here to warn that we have something funky happening using some APIs that haven't yet become official? Is there concern of this confusing an end user to think something is in a broken state, when this is actually expected and things are OK?
Runtime Status
Activation
Activated by onWalkthrough:konveyor-setup event: 0ms
Messages (2)
diffEditor/gutter/selection is a proposed menu identifier. It requires 'package.json#enabledApiProposals: ["contribDiffEditorGutterToolBarMenus"]' and is only available when running out of dev or with the following command line switch: --enable-proposed-api konveyor.konveyor-ai
diffEditor/gutter/hunk is a proposed menu identifier. It requires 'package.json#enabledApiProposals: ["contribDiffEditorGutterToolBarMenus"]' and is only available when running out of dev or with the following command line switch: --enable-proposed-api konveyor.konveyor-ai
The text was updated successfully, but these errors were encountered:
permanently add our extension to privileged extensions in the VS Code internal config(after every update):
# on Linux under /usr/share/code/resources/app/product.json
"extensionEnabledApiProposals": {
"konveyor.konveyor-ai":["contribDiffEditorGutterToolBarMenus"],
Version: 0.0.10
When I bring up "Runtime Status", I see the below 2 messages relating to the 'proposed api' usage for diff/merge view.
I'm filing this issue to see what team thinks about this, do we want to keep the messages displayed here to warn that we have something funky happening using some APIs that haven't yet become official? Is there concern of this confusing an end user to think something is in a broken state, when this is actually expected and things are OK?
The text was updated successfully, but these errors were encountered: