Skip to content

Commit 080ed43

Browse files
authored
fix: replace dead link to JSON Schema ref parser website
The JSON Schema ref parser website is now available under a different domain. Therefore the link to it must be adapted.
1 parent 5773704 commit 080ed43

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/docs/deprecated/ref-resolving-legacy.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ ajv.addSchema(yourSchemaObject, 'yourSchemaIdentifier');
2929

3030
Next, we'll set up the ref resolver. The implementation is up to you, but you'll need to implement a `canRead` method that determines whether a current ref needs to be resolved and a `read` method that returns the actual schema.
3131
The `order` property determines the order in which resolvers are executed, until the first one returns true for `canRead`.
32-
For more info about ref resolving please see the [JSON Schema \$Ref parser documentation](https://apidevtools.org/json-schema-ref-parser/docs/plugins/resolvers.html).
32+
For more info about ref resolving please see the [JSON Schema \$Ref parser documentation](https://apitools.dev/json-schema-ref-parser/docs/plugins/resolvers.html).
3333
Note that the name for the actual resolver, which we called `foo` here, does not actually matter.
3434

3535
```js

0 commit comments

Comments
 (0)