Describe the bug
The value "information" for any of the "report(...)" keys in the filepyrightconfig.json raises a problem
Incorrect type. Expected "boolean". in the problem panel but it works using such severity setting (see 2nd screenshot below).
To Reproduce
Easy to reproduce with above description.
Expected behavior
"information" is registered as valid value for such "report(...)" keys (see at the bottom of this report).
It would also be great, to have some more informative and complete suggestion via IntelliSense. At the moment it is missing "information" in the suggestions list of IntelliSense and some description (assume that can be set in the package.json) for all possible values would help the user:
Screenshot showing that "information" is not suggested and that the description (here "Default value") could be more informative:

Screenshots or Code

VS Code extension or command-line
VS Code extension 1.1.53
Additional context
Probably that is just a minor change for the value of the definitions key here
Maybe replace
{
"definitions": {
"diagnostic": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "string",
"enum": [
"none",
"warning",
"error"
]
}
]
}
}
}
by something like
{
"definitions": {
"diagnostic": {
"anyOf": [
{
"type": "boolean",
"enum": [
false,
true
],
"enumDescriptions": [
"Disable this message category",
"Enable this message category using its default severity level"
]
},
{
"type": "string",
"enum": [
"error",
"information",
"none",
"warning"
],
"enumDescriptions": [
"Set the severity level for this message category to \"error\".",
"Set the severity level for this message category to \"information\".",
"Disable this message category.",
"Set the severity level for this message category to \"warning\"."
]
}
]
}
}
}
Thanks for the bug report. We forgot to add it to the JSON schema. It will be fixed in the next version. In the meantime, you can simply ignore the warning in the JSON editor.
This is now fixed in Pyright 1.1.54, which I just published.