Skip to content

Invalid JSON escaping in cargo-util-schemas #14999

Closed
@fruzitent

Description

@fruzitent

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)

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


Metadata

Metadata

Assignees

No one assigned

    Labels

    C-bugCategory: bugS-triageStatus: This issue is waiting on initial triage.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions