json-schema-ref-parser icon indicating copy to clipboard operation
json-schema-ref-parser copied to clipboard

Parse, Resolve, and Dereference JSON Schema $ref pointers in Node and browsers

Results 105 json-schema-ref-parser issues
Sort by recently updated
recently updated
newest added

Currently the library can only parse keys with the name `$ref`. This matches the JSON Schema specifications, but sometimes it may be useful to rename the key to for example...

hi there, I stumbled upon a small bug which occurs when all the following are true (I am sure there are other variations of loading multiple schemas that trigger the...

All, I'm having an issue resolving a reference. Having tested a couple scenarios, I was happy to see that providing a top-level reference and included some other properties alongside the...

bug

To reproduce, create `test.js` somewhere: ```js var parser = require( 'json-schema-ref-parser' ); var path = require( 'path' ); parser.dereference( path.join( __dirname, 'test.yaml' ) ); ``` Running `test.js` from `cmd` in...

bug

I've got a schema with absolute urls to resources with no port number in the URL... ```json { "$schema": "http://json-schema.org/draft-04/schema#", "id": "http://localhost/schema/01/plantdb.json", "type": "object", "properties": { "names": {"$ref": "http://localhost/schema/01/names.json"} }...

I have the latest npm package 9.0.9 installed. excludedPathMatcher functionality is missing in this version of the npm package. Source was updated 6 months ago to include this but no...

Module not found: ESM packages (node-fetch) need to be imported. Use 'import' to reference the package instead. Next 14 Apple silicon M2 Next Build Anyone running into this issue??

Hi~ I have schema like this ```json { "type": "object", "definitions": { "upload": { "s-props": { "a": "a" } } } } ``` ```json { "type": "object", "properties": { "upload":...

https://github.com/APIDevTools/json-schema-ref-parser/blob/26d824b4b230f4ce2471f73401a4b6f7c7c67ac2/lib/util/convert-path-to-posix.ts#L10 win32 is not supported withe the path-browserify polyfill. This currently causes a null failure. Cannot read properties of null (reading 'sep') at convertPathToPosix (convert-path-to-posix.js:12:1)

file1.json: { "swagger": "2.0", "paths": { "/:analyze-text": { "post": { "parameters": [ { "$ref": "common.json#/parameters/ApiVersionParameter" } ], "responses": { "default": { "description": "Unexpected error", "schema": { "$ref": "common.json#/definitions/ErrorResponse" } }...