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
#14683 introduces generation of schema for Cargo.toml. However, it's not a valid JSON.
Steps
$ cat manifest.schema.json | jq
jq: parse error: Invalid numeric literal at line 989, column 105
Possible Solution(s)
diff --git a/manifest.schema.json b/manifest.schema.json.1
index a7ea5bd..020be02 100644
--- a/manifest.schema.json+++ b/manifest.schema.json.1@@ -986,11 +986,11 @@
"TomlDependency_for_String": {
"anyOf": [
{
- "description": "In the simple format, only a version is specified, eg. `package = /"<version>/"`",+ "description": "In the simple format, only a version is specified, eg. `package = \"<version>\"`",
"type": "string"
},
{
- "description": "The simple format is equivalent to a detailed dependency specifying only a version, eg. `package = { version = /"<version>/" }`",+ "description": "The simple format is equivalent to a detailed dependency specifying only a version, eg. `package = { version = \"<version>\" }`",
"allOf": [
{
"$ref": "#/definitions/TomlDetailedDependency_for_String"
Notes
No response
Version
The text was updated successfully, but these errors were encountered:
Problem
#14683 introduces generation of schema for Cargo.toml. However, it's not a valid JSON.
Steps
$ cat manifest.schema.json | jq jq: parse error: Invalid numeric literal at line 989, column 105
Possible Solution(s)
Notes
No response
Version
The text was updated successfully, but these errors were encountered: