tangram-js / json-schema-editor Goto Github PK

There's an error in your website where the first link to the github project leads to https://github.com/idjhuang/json-schema-editor

This and the note about Json Editor being a successor of Json Schema Editor lead me to believe, that Json Schema Editor is discontinued.

Perhaps you could clarify this.

Given I add a "definitions" section with reusable schemas to the main schema
Then the "definitions" are not rendered in the right panel
And the "definitions" are not saved and restored on load
Unless I move the "definitions" section up using the context menu in the tree editor
But then the main schema is not shown
And the main schema is not saved and restored on load

if the file being loaded has an enum with an array, loading fails with error unexpected character
{
"type": "string",
"enum": [
"test"
],
"title": "schema"
}

if we remove the enum, everything starts working again

When I add to a string or integer type an enum, the enum should be an array like this:
"type": "string", "enum": { "enum": [ "true" ] }
But it is wrong because it should be generated as an array without being wrapped with an "enum" object.
The right way should be something like this:
"type": "string", "enum": [ "true" ]

I'm wondering if there are any plans to expand the app to plug in other DB solutions (Postgres, Mongo, etc). It would be great to DBs outside of Firebase when required.

Uncaught Error: FIREBASE FATAL ERROR: Cannot parse Firebase url. Please use https://.firebaseio.com

When I try to write the maximum value of a number it give me always the same error : Please input number.

It appears that something as simple as the following isn't supported:

{
 "$id": "https:/com.foo.test.json",
 "$schema": "http://json-schema.org/draft-07/schema#",
 "definitions": {
   "aType": {
     "$id": "#aType",
     "description": "A Type",
     "type": "object",
     "allOf": [
       {
         "$ref": "#otherType"
       }
     ],
     "properties": {
       "field1": {
         "description": "A field",
         "type": "string"
       }
     }
   },
   "otherType": {
     "$id": "#otherType",
     "description": "Another type",
     "type": "object",
     "properties": {
       "field2": {
         "description": "A field",
         "type": "string"
       }
     }
   }
 }
}

The "allOf" construct in aType is simply dropped when importing this schema, and there is no way to create a schema with this structure in the editor.

A similar problem exists for "oneOf", "anyOf" and "not".

The editor does support a roughly equivalent structure of using a "oneOf" and nesting the object properties below this, but this doesn't help when trying to import existing schemas that already use the simpler approach.

For a key/value map structure, like {"web":8000,"api":8001}, I can't find how to apply a schema to the values regardless of key. Ideally a full object schema could be applied to specify a rich map data structure.

ref: https://stackoverflow.com/questions/22229250/how-to-create-json-schema-for-name-value-structure#comment60712837_22232419

Support for const keyword would be nice to have .
For example :

    "type": "object",
    "additionalProperties": true,
    "properties": {
        "RequestTypeId": {
	   "type": "number",
            "const": 4
        },

When a required property is deleted, it is not being excluded from the required list.

It would be nice if you could add a title to a property.

https://json-schema.org/draft/2020-12/json-schema-validation.html#rfc.section.9.1

If I want to add the following object in my schema:
"prop(1)": { "type": "number", "minimum": 5, "maximum": 10, "enum": [100] }
The following error will appear

should be <= 10

although that's not supposed to be!

The "load from file" feature for the schema editor is failing with the following error:

Load schema from file error: Cannot set property 'name' of undefined

The file was created using the editor and downloaded prior to attempting to load.

When importing a schema that has a property with a key named "type" the editor reports an error:
Load schema from file error: JSON.parse: expected ',' or '}' after property value in object at line 83 column 7 of the JSON data

The property looks like this:
"Membership": {
"type": "object",
"properties": {
"level": {
"description": "Status or level of membership.",
"type": "string"
},
"name": {
"description": "The name of the membership.",
"type": "string"
},
"number": {
"description": "The membership number assigned to the member.",
"type": "string"
},
"type": {
"description": "The type of membership.",
"type": "string"
}
}

It's not possible to create schema definitions to be reused. Instead each has to be a separated file using the ref repository

If add an enum property to an object it's represented like this:

 "end_code_type": {
            "enum": [
                "QRCODE",
                "NFCTAG",
                "BEACON"
            ]
        },

After saving and reloading the same schema the property looks like this:

       "end_code_type": [
            "QRCODE",
            "NFCTAG",
            "BEACON"
        ],

I have made several schemas and saved them on the website. After logging out and logging back in, they are not listed. If I upload from file or try to save a new schema of the same name, I receive the dialog that the existing schema will update. I did not download one of my schemas and would like to be able to access it. Is there anything I can do to do so?

According to the reference guide (https://json-schema.org/understanding-json-schema/reference/numeric.html#range) the valid values for defining ranges are:

• minimum
• maximum
• exclusiveMinimum
• exclusiveMaximum

The current version of the schema editor currently sets the excludeMinimum and excludeMaximum properties to a boolean value. I believe this to be incorrect as I can not find any references in the json schema RFC to these values. I believe this to be an issue that needs to be corrected.

Please let me know if any additional information is required.

Save custom schema error: Firebase.set failed: First argument contains an invalid key ($ref) in property 'schemas.xOW3vBZG7JSxJcqfilsEdUJ0ZnI2.Pool.items.0'. Keys must be non-empty strings and can't contain ".", "#", "$", "/", "[", or "]"

{
"type": "array",
"items": [
{
"$ref": "repository://Pool_member"
}
],
"title": "Pool",
"description": "Pool"
}

The minimum property gets removed if its value is set to 0. This makes it impossible to restrict integers or numbers to only positive values.

I've tried to import a schema with definitions but it does not work.

How to reproduce

Just import a schema like bootstraprc.json

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "title": "JSON schema for Webpack's bootstrap-loader configuration file",
  "type": "object",

  "definitions": {
    "extractStyling": {
      "type": "object",
      "properties": {
        "extractStyles": {
          "default": false,
          "description": "Enables/disables extraction of styles to a standalone CSS file using extract-text-webpack-plugin",
          "type": "boolean"
        }
      }
    },

    "coreProperties": {
      "type": "object",

      "properties": {
        "appStyles": {
          "description": "Import your custom styles here. Usually this endpoint file contains a list of @imports of your application styles.",
          "type": "string"
        },
        "bootstrapCustomizations": {
          "description": "The .scss file path to be loaded after Bootstrap's _variables.scss file",
          "type": "string"
        },
        "bootstrapVersion": {
          "default": 3,
          "description": "The major version of Bootstrap being used",
          "enum": [ 3, 4 ],
          "type": "integer"
        },
        "loglevel": {
          "description": "The verbosity of logging. Exclude this property to disable.",
          "enum": [ "debug" ],
          "type": "string"
        },
        "preBootstrapCustomizations": {
          "description": "The .scss file path to be loaded before Bootstrap's _variables.scss file",
          "type": "string"
        },
        "scripts": {
          "description": "Excludes/includes Bootstrap's JavaScript modules",
          "type": [ "boolean", "object" ]
        },
        "styleLoaders": {
          "default": [ "style", "css", "sass" ],
          "description": "An array of Webpack loader names. Order matters, and sass-loader is required.",
          "items": {
            "type": "string"
          },
          "minItems": 1,
          "type": "array",
          "uniqueItems": true
        },
        "styles": {
          "description": "Excludes/includes Bootstrap's CSS modules",
          "type": [ "boolean", "object" ]
        },
        "useCustomIconFontPath": {
          "default": false,
          "description": "Set to true if using a custom icon font and you need to specify its path in your Sass files",
          "type": "boolean"
        },
        "useFlexbox": {
          "default": true,
          "description": "Enables/disables the flexbox model available in Bootstrap 4",
          "type": "boolean"
        }
      }
    }
  },

  "allOf": [
    {
      "$ref": "#/definitions/coreProperties"
    },
    {
      "anyOf": [
        {
          "properties": {
            "env": {
              "description": "Sets the extractStyles property based on the value of NODE_ENV",
              "type": "object",
              "properties": {
                "development": {
                  "$ref": "#/definitions/extractStyling"
                },
                "production": {
                  "$ref": "#/definitions/extractStyling"
                }
              }
            }
          },
          "not": {
            "properties": {
              "extractStyles": { }
            },
            "required": [ "extractStyles" ]
          }
        },
        {
          "properties": {
            "extractStyles": {
              "$ref": "#/definitions/extractStyling/properties/extractStyles"
            }
          },
          "not": {
            "properties": {
              "env": { }
            },
            "required": [ "env" ]
          }
        }
      ]
    },
    {
      "required": [ "bootstrapVersion", "styleLoaders" ]
    }
  ]
}

For those who aren't expert with Node.js, it would be lovely if you provided a Docker image so that we could install the editor w/o having to install all of its dependencies locally.

Hi there,

I've been looking for a way to embed a json schema editor into a project of mine (Happens to be made in Vue 2 aswell), and i came accross your repository here.

Is there any chance that this project could be made into a view componet/component lribary? That would make it much easier for this to be embeded into existing applications.

If not, would it be alright for me to fork this, and turn it into a component library?