Commit 1ce418cf authored by Stephane Nicoll's avatar Stephane Nicoll

Fix meta-data for logging.level property

parent 924b9f9d
......@@ -511,7 +511,7 @@ Since a logger name can be any arbitrary name, really, this provider should allo
value but could highlight valid packages and class names that are not available in the
project's classpath.
The meta-data snippet below corresponds to the standard `logger.level` property, keys
The meta-data snippet below corresponds to the standard `logging.level` property, keys
are _logger names_ and values correspond to the the standard log levels or any custom
level:
......@@ -519,7 +519,7 @@ level:
----
{"hints": [
{
"name": "logger.level.keys",
"name": "logging.level.keys",
"values": [
{
"value": "root",
......@@ -533,7 +533,7 @@ level:
]
},
{
"name": "logger.level.values",
"name": "logging.level.values",
"values": [
{
"value": "trace"
......
......@@ -115,7 +115,7 @@
}
],"hints": [
{
"name": "logger.level.keys",
"name": "logging.level.keys",
"values": [
{
"value": "root",
......@@ -129,7 +129,7 @@
]
},
{
"name": "logger.level.values",
"name": "logging.level.values",
"values": [
{
"value": "trace"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment