Skip to content

Conversation

andxu
Copy link
Contributor

@andxu andxu commented Nov 7, 2017

No description provided.

@@ -217,6 +223,57 @@ function configLogLevel(level) {
return commands.executeJavaLanguageServerCommand(commands.JAVA_CONFIG_LOG_LEVEL, convertLogLevel(level));
}

interface IDebugSettings {
show_hex?: boolean;
Copy link
Contributor

Choose a reason for hiding this comment

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

Use Camel to keep name convention consistent.


function collectDebugSettings(): IDebugSettings {
const settings: IDebugSettings = {};
if (vscode.workspace.getConfiguration().get("java.debug.settings.showHex")) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Cannot set the value to false. no need to if.

package.json Outdated
},
"java.debug.settings.showHex": {
"type": "boolean",
"default": false
Copy link
Contributor

Choose a reason for hiding this comment

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

add description here.

testforstephen
testforstephen previously approved these changes Nov 8, 2017
README.md Outdated
@@ -69,6 +69,10 @@ Please also check the documentation of [Language Support for Java by Red Hat](ht
### User Settings

- `java.debug.logLevel`: minimum level of debugger logs that are sent to VS Code, defaults to `warn`.
- `java.debug.settings.showHex`: whether or not the number should be displayed as hex format in variable view, defaults to `false`.
Copy link
Member

Choose a reason for hiding this comment

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

show integers in hex format

README.md Outdated
@@ -69,6 +69,10 @@ Please also check the documentation of [Language Support for Java by Red Hat](ht
### User Settings

- `java.debug.logLevel`: minimum level of debugger logs that are sent to VS Code, defaults to `warn`.
- `java.debug.settings.showHex`: whether or not the number should be displayed as hex format in variable view, defaults to `false`.
- `java.debug.settings.showStaticVariables`: whether or not the static variables will be displayed in variable view, defaults to `true`.
Copy link
Member

Choose a reason for hiding this comment

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

show static variables in "Variables" viewlet

README.md Outdated
@@ -69,6 +69,10 @@ Please also check the documentation of [Language Support for Java by Red Hat](ht
### User Settings

- `java.debug.logLevel`: minimum level of debugger logs that are sent to VS Code, defaults to `warn`.
- `java.debug.settings.showHex`: whether or not the number should be displayed as hex format in variable view, defaults to `false`.
- `java.debug.settings.showStaticVariables`: whether or not the static variables will be displayed in variable view, defaults to `true`.
- `java.debug.settings.showQualifiedNames`: whether or not the class name should be displayed using the fully qualified class name, defaults to `false`.
Copy link
Member

Choose a reason for hiding this comment

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

show fully qualified class names

package.json Outdated
},
"java.debug.settings.showHex": {
"type": "boolean",
"description" : "whether or not the number should be displayed as hex format in variable view",
Copy link
Member

Choose a reason for hiding this comment

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

Please change the descriptions accordingly.

Copy link
Member

Choose a reason for hiding this comment

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

Same for below ones.

README.md Outdated
@@ -69,6 +69,10 @@ Please also check the documentation of [Language Support for Java by Red Hat](ht
### User Settings

- `java.debug.logLevel`: minimum level of debugger logs that are sent to VS Code, defaults to `warn`.
- `java.debug.settings.showHex`: show the number in hex format in variable view, defaults to `false`.
Copy link
Member

Choose a reason for hiding this comment

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

show numbers in hex format in "Variables" viewlet, de...

README.md Outdated
@@ -69,6 +69,10 @@ Please also check the documentation of [Language Support for Java by Red Hat](ht
### User Settings

- `java.debug.logLevel`: minimum level of debugger logs that are sent to VS Code, defaults to `warn`.
- `java.debug.settings.showHex`: show the number in hex format in variable view, defaults to `false`.
- `java.debug.settings.showStaticVariables`: show the static variables in variable view, defaults to `true`.
- `java.debug.settings.showQualifiedNames`: show the fully qualified class name in variable view, defaults to `false`.
Copy link
Member

Choose a reason for hiding this comment

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

class names.

akaroml
akaroml previously approved these changes Nov 9, 2017
README.md Outdated
@@ -69,6 +69,10 @@ Please also check the documentation of [Language Support for Java by Red Hat](ht
### User Settings

- `java.debug.logLevel`: minimum level of debugger logs that are sent to VS Code, defaults to `warn`.
- `java.debug.settings.showHex`: show numbers in hex format in "Variables" viewlet, defaults to `false`.
- `java.debug.settings.showStaticVariables`: show static variables in "Variables" viewlet, defaults to `true`.
- `java.debug.settings.showQualifiedNames`: show the fully qualified class names in "Variables" viewlet, defaults to `false`.
Copy link
Member

Choose a reason for hiding this comment

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

remove "the" before fully....

@andxu andxu merged commit 96f2b7c into master Nov 9, 2017
@andxu andxu deleted the andy_user_settings2 branch November 9, 2017 06:43
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