-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
9012-vscode-java-debug-error #9035
9012-vscode-java-debug-error #9035
Conversation
Issues this PR solves: 1) vscode-java-debug invokes vscode.window.registerTerminalLinkProvider upon extension activation. This method was not implemented in Theia - added it but implementation itself seems like an entire PR and don't know if it is wanted in this PR. 2) after crossing issue #1, second problem was that JDTUtils threw exception when receiving file changed event where URI scheme was user_storage - illegal schema name (_) Signed-off-by: Dan Arad <dan.arad@sap.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danarad05 thank you for the pull-request, can you please update both the commit and pull-request description by including a proper link to the issue (not #1
). It seems the link provided for the user-storage
update is incorrect.
In addition, it might be better to separate the pull-request into two commits (stubbing terminal-link
and updating user-storage
). The commit title "9012-vscode-java-debug-error" does not help to accurately reflect the changes when viewing the git history.
* A provider that enables detection and handling of links within terminals. | ||
*/ | ||
// copied from https://github.com/microsoft/vscode/blob/bd20a720fba05f87ddb53c11c6af66936fd88a55/src/vs/vscode.d.ts#L5578-L5597 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor: remove unnecessary line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed. please see #9048
@@ -23,7 +23,7 @@ import { PreferenceConfigurations } from '@theia/core/lib/browser/preferences/pr | |||
import { PreferenceScope } from '@theia/core/lib/browser'; | |||
|
|||
const PREFERENCE_URI_PREFIX = 'vscode://schemas/settings/'; | |||
const USER_STORAGE_PREFIX = 'user_storage:/'; | |||
const USER_STORAGE_PREFIX = 'user-storage:/'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand that _
is not valid according to RFC 3986, but I'm not sure what the implications or side effects of changing the scheme are (it should most definitely be reported in the changelog).
For instance we should confirm that:
- existing user preferences, extensions, keymaps can still be loaded from the user's home
- any other potential use-cases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vince-fugnitto
added remark in changelog - please see #9049 for that.
tested prefs, exts, keymaps and seems that scheme change works fine.
|
Split this PR to two (as per @vince-fugnitto's request) - #9048 #9049. Therefore closing this PR. |
Signed-off-by: Dan Arad dan.arad@sap.com
What it does
(a) Fixes #9012
(b) this PR solves:
user_storage
touser-storage
scheme nameHow to test
Review checklist
Reminder for reviewers