A collection of JSON schema files including full API
Home Page: http://schemastore.org
License: Apache License 2.0
The largest collection of independent JSON schemas in the world.
The repository is a universal JSON schema store, where schemas for popular JSON documents can be found.
Website: schemastore.org
Contributions are more than welcome! Both to the website itself or to the various schema files. Please carefully read CONTRIBUTING.md.
Be good can install as package and load schema from package. Maybe best good create two repo one have only schamas, other have only web site
Would like support for .editorconfig INI-style config files.
This one is a little different because it's not exactly JSON and I didn't see any support for anything similar but it seems like these kinds of things could be supported without too much work.
Thoughts?
Hi
I've completed the first cut of a JSON Schema documentation tool. Basically it creates HTML and PDF documentation from a json schema (draft 4). Note its not 100%, finished, but good enough to demo!
I've generated the code for most of the schemas in your library, and hosted it on our site (see http://schemas.liquid-technologies.com/json/.angular-cli.json/index.html for example).
I've also mocked up the changes required to link to it from the schemastore, see
https://github.com/sprotty/schemastore
If you think the documentation is useful then please get in touch to discuss it (
). It is still early days with the document generator, so I'm in a good position to incorporate feedback, changes, enhancements etc.
Regards
Simon
Would like support for .eslintrc files.
From @saschanaz on January 3, 2017 7:26
Steps to Reproduce:
jsconfig.jsoncompilerOptions and targetes6 by default whereas the name es2015 is now preferredCopied from original issue: microsoft/vscode#18023
The intent of "directive-selector-prefix" and "component-selector-prefix" in tslint.json files is to allow people to turn the prefix check on/off, and then define a custom prefix to use. "sg" is used as the custom prefix in some samples because it was in some Style Guides that way, but it was never intended to be the only possible value.
In http://json.schemastore.org/tslint, these two properties need to be changed so that their arrays will accept true, false, or any string.
pipe-naming, likewise, needs to allow true/false (for the first value), "kebabCase"/"camelCase" (for the second), and any string (for the remaining values).
Here's an example of the plugins of .babelrc accepting more than just strings:
.babelrc
{ "plugins": [ ["react-intl", { "messagesDir": "./build/messages/", "enforceDescriptions": true }] ] }
Plugin Options
Plugins can specify options. You can do so in your config by wrapping it in an array and providing a options object. For example:
{ "plugins": [ ["transform-async-to-module-method", { "module": "bluebird", "method": "coroutine" }] ] }
The babelrc.json here says:
"plugins": {
"description": "List of plugins to load and use",
"type": "array",
"items": {
"type": "string"
}
},
I think it should be this:
"type": ["string", "array"],
"items": {
"description": "the plugin name in .[0] and the options object in .[1]",
"type": [ "string", "object" ]
}
object-literal-sort-keys presently only accepts a boolean, resulting in this error in VSCode:
TSLint's ruleset allows for both boolean or boolean/string configuration: https://palantir.github.io/tslint/rules/object-literal-sort-keys/
Relates to other inconsistent settings in #245.
TSLint: 5.4.3
VSCode: 1.13.1
VSCode TSLint Extention: 0.16.0
From @cyrilletuzi on May 30, 2017 14:28
Steps to Reproduce:
"checkJs": true in jsconfig.json > type checking is working and json is OK"strict": true in jsconfig.json > strict type checking is working but json is warned as invalid as strict property is missing in jsconfig.json schema.I can manage the PR, but I didn't found the file (I just found the one with the default values, but not the schema itself).
Copied from original issue: microsoft/vscode#27583
Hello, guys,
Firstly, this project is very interesting. You simplify the process of writing configs in Visual Studio Code. Thanks, 👍
Secondly, I write schema generator for stylelint. Before generate the schema, i would like to clarify a few questions:
How detailed should I make the schema? For example, now I'm writing: example.json (rule: font-weight-notation)or i should use a simplified version as eslintrc.json#L8-L27?
Can I provide the following information: if array then first item should be string and second item should be object?
{
"rules": {
"font-weight-notation": ["numeric", { "ignore": ["relative"] }]
}
}I personally do not know enough about this to provide much more information, but please see https://github.com/shinnn/vscode-stylelint/issues/98
I have noticed the following inconsistencies:
member-ordering should include the a definition of the object that is allowed, and string is no longer one of the allowed types, as per the tslint documetationno-consecutive-blank-lines should allow an array or just a boolean value, as per the tslint documentationno-inferrable-types should allow just a boolean value in addition to an array, as per the tslint documentationI need some assistance adding a schema to the schemastore repository and couldn't find the information I needed in the project documentation. I would appreciate any assistance that you can provide, and think that answers to these questions would be a good addition to either the README.md or some other documentation in the repository.
I am attempting to add schema for some ArcGIS JSON formats: ArcGIS Web Map Data and ArcGIS Online Item. (I am attempting this in this fork and branch.) I also created another JSON Schema file for geometry objects that is referenced by the other two files. Although the schema files seem to work correctly within the Visual Studio 2015 IDE environment, referencing the external geometry JSON Schema file is causing an error in the Grunt build task.
Running "tv4:arcgis-online-item" (tv4) task
> load + arcgis-geometry.json
Process terminated with code 3.
Fatal error: Cannot call method 'replace' of undefined
If I understand correctly, the schema validation task is successful. It is the task that validates the sample data against JSON Schema that is failing. (It's possible this also may be a bug with grunt-tv4.)
The .babelrc schema needs to allow arrays as values in the presets array. Currently it only allows strings.
{
"presets": [
[ "es2015", { "modules": "umd" } ]
]
}This would be conform with regular JSON schema and it would enable all the features of JSON pointers. You could use it to refer to local files, for example, which is what I'm currently after.
the web-manifest schema describes "uri" as the format for start_url and icon.src, but I don't think this is compatible with what the the Manifest spec describes where these URIs are potentially relative URIs.
(I understand that the jsonschema validation spec requires uri to match absolute URIs per its reference to RFC 3986).
The TypeScript compiler treats the compiler options such as module and target case insensitive. The tsconfig.json schema however can not express that and lists enum value in lower case. Because of that, all options using a different casing are considered invalid.
This causes issues such as microsoft/vscode-generator-code#20.
The schema should be changed to either
ES3, ES5 and ES6 for target as they are explicitly named in the TS documentation "module": {
"description": "Specify module code generation: 'CommonJS', 'Amd', 'System', 'UMD', 'es6', or 'es2015'.",
"oneOf": [{
"enum": [ "commonjs", "amd", "umd", "system", "es6", "es2015" ]
}, {
"type": "string"
}],
}Hi Mads,
are there any plans on creating a schema for Twitter Json?
https://dev.twitter.com/rest/public
Thanks
Michael
Could it because of $schema is ahead of title?
https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/typings.json#L2
Compare to others, (e.g. tsconfig.json), it's the other way around:
https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/tsconfig.json#L2
I understand that it's json and order should not matter, but I can't see other reason for it.
Can I make a PR to give it a try? Or do you know how to get a local copy and try it out?
Both tsconfig and jsconfig files support a plugins property in the compilerOptions. However it is currently only documented for tsconfig files
I'll submit a PR that also adds this property to the jsconfig schema
http://schemastore.org/api/json/catalog.json
{
"name": "ui5-manifest",
"description": "UI5/OPENUI5 descriptor file",
"fileMatch": [
".manifest"
],
"url": "http://json.schemastore.org/ui5"
}
http://json.schemastore.org/ui5 returns a 404
You should consider having an automated unit test that checks every entry in catelog.json returns 200.
http://jshint.com/docs/options/#unused
"unused": {
"description": "Require all defined variables be used",
"type": [ "boolean", "string" ],
"enum": [ true, false, "vars", "strict" ]
}
Would like secure access to the schemas, but trying to access schemastore from an https served app gives:
This server could not prove that it is json.schemastore.org; its security certificate is from *.azurewebsites.net. This may be caused by a misconfiguration or an attacker intercepting your connection.
I'm using VSCode 1.7.2, TSLint plugin 0.6.3, TSLint 4.0.1 and TypeScript 2.0.10.
When I open the tslint.json file in VSCode I get serveral wrong warnings about my configuration values:
"cyclomatic-complexity": true -> Incorrect type. Expected "array"
"no-consecutive-blank-lines": true -> Incorrect type. Expected "array"
"object-literal-key-quotes": [true, "consistent-as-needed"] -> Value is not an accepted value. Valid values: [true,false,"always","as-needed"]
"one-variable-per-declaration": true -> Incorrect type. Expected "array"
"only-arrow-functions": true -> Incorrect type. Expected "array"
"typedef": [true, "arrow-call-signature"] -> Value is not an accepted value. Valid values: [true,false,"call-signature","parameter","arrow-parameter","property-declaration","variable-declaration","member-variable-declaration"]
The JSCS schema definition is outdated. For example maximumLineLength now also allows an Object value.
http://jscs.info/rule/maximumLineLength.html
But there are also other outdated settings.
"exclude": [
"node_modules",
"bower_components"
]
excludes files or folders, no globs allowed.
The TSLint documentation has a property that is missing from the schema.
defaultSeverity?: "error" | "warning" | "off": The severity level used when a rule specifies a default warning level. If undefined, “error” is used. This value is not inherited and is only applied to rules in this file.
Suggested fix:
Add the following object to the properties section at the end of the schema:
"defaultSeverity": {
"type": "string",
"enum": ["error", "warning", "off"],
"default": "error"
}
With new options coming in TypeScript 2.0, is there a way to specify that these flags are only for certain TypeScript version and that only when certain version of TypeScript is installed, those flags will be shown
It wasn't clear to me from the README that you can do so
Versioning of schema files are handled by modifying the file name to include the version number: myschema-1.2.json
Thanks!
1st thing we read -> should fix it !
While writing the doc about the project.json schema (dotnet/docs#448), I've noticed a few things that need to be fixed in the schema file:
From @OliverJAsh on April 16, 2016 16:45
When a package.json has private: true, my understanding is that it shouldn't require a name or a version.
Copied from original issue: microsoft/vscode#5398
Is there any interest in creating RC1- and RC2-specific JSON schemas for project.json? As an example, the compilationOptions property is now deprecated in RC2 in favor of buildOptions. Cases like this may prove the value of such versioning.
To me it looks like entries in https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catalog.json are mostly sorted by name but not all. Please state where new schemas should be added in PRs. Obvious possibilities would be: At the end of the list (like I did in #174 ), sorted into the list by name
The schema at http://xunit.github.io/schema/v2.1-rc1/xunit.runner.schema has been deleted.
Needs to be removed from https://github.com/SchemaStore/schemastore/blob/master/src/api/json/catalog.json
The current definition for response.body does not allow you to return top level array
"response.body": {
"description": "The string representation of the body to be returned to the client.",
"anyOf": [
{ "type": "string" },
{ "type": "object" }
]
},
Would like support for .babelrc JSON-style config files.
Angular Cli recently released a stable version 1.0.0
I'd like to contribute or ask if the schema for the .angular-cli.json configuration file can be added.
Here it is:
https://github.com/angular/angular-cli/blob/master/packages/@angular/cli/lib/config/schema.json
I notice the content-type of the JSON schemastore delivering is text/plain instead of application/json.
It can be a problem for file request management and dynamic parsing.
Content-Type: application/json
The "latedef" option should allow the string "nofunc".
http://json.schemastore.org/sourcemap-v3.json is using default to provide a description instead of description for sourceRoot and file, which is bad for IntelliSense. I wanted to improve it but cannot find the schema in the repo?
The exportsOverride property in bower.json should allow arrays for the file globbing values.
E.g.
"exportsOverride": {
"jquery-validation": {
"": [ "jquery.validate.js", "additional-methods.js" ]
}
}I was surprised that SchemaStore doesn't have a schema for geoJSON. Is this in the works? Or would there be interest in creating one?
Since more and more projects/frameworks are using YAML as their configuration format and it's fairly easy to apply JSON Schema to YAML, I think it would make a lot of sense to add a new section YAML to the schemastore.
Would you be open to this idea? I'd love to contribute a couple of schemas for popular frameworks and tools.
According to the docs: https://palantir.github.io/tslint/rules/indent/
A second optional argument specifies indentation size:
In the schemastore tslint schema requires all:
"indent": [ true, "tabs"], // Invalid by schema while correct
"indent": [ true, "tabs", 4], // No complain, but redundant.The schema http://json.schemastore.org/function does not match the set of values defined on the azure portal for Service Bus bindings to azure functions. I suppose each "in" and "out" direction should have their own set, i.e. [manage,listen] and [manage,send] respectively.
socket in permissions is an object with an array, but expect as string
=>{"socket": ["rule1", "rule2"]}
I've noticed the below schema's pointing to githubusercontent.com cannot be loaded through ajax:
XMLHttpRequest cannot load https://raw.githubusercontent.com/composer/composer/master/res/composer-schema.json. The 'Access-Control-Allow-Origin' header has a value 'https://render.githubusercontent.com' that is not equal to the supplied origin. Origin 'http://localhost:8080' is therefore not allowed access.
XMLHttpRequest cannot load https://raw.githubusercontent.com/mozilla/contribute.json/master/schema.json. The 'Access-Control-Allow-Origin' header has a value 'https://render.githubusercontent.com' that is not equal to the supplied origin. Origin 'http://localhost:8080' is therefore not allowed access.
XMLHttpRequest cannot load https://raw.githubusercontent.com/wordnik/swagger-spec/master/schemas/v1.2/apiDeclaration.json. The 'Access-Control-Allow-Origin' header has a value 'https://render.githubusercontent.com' that is not equal to the supplied origin. Origin 'http://localhost:8080' is therefore not allowed access.
Maybe it's useful to host them at schemastore by default unless a schema provider serves the schema from a stable source on their own website?
If I recall correctly github deliberatly does not support this kind of loading, since it's not a cdn.
I'm just fooling around with the schemastore btw, so the priority of this issue is zero :-)
I just expected every schema to be reachable without any extra coding.
I'm using this catalog as source:
http://schemastore.org/api/json/catalog.json
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.