You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I originally thought this might be related to #30, however I now do not think it is.
I'm using Fastify v2.14.1, and I instantiate my own AJV and configure it using .addSchema(...). I then use the $id references from my manually loaded schemas when creating my route schemas. This works fine in Fastify, and I can tell the schemas are being validated at runtime.
However, when using the plugin UI, and navigating into a particular route, I get the following error, when the schema reference is attempted to be resolved.
Resolver error at paths./events.post.requestBody.content.application/json.schema.properties.rulesets.items.$ref
Could not resolve reference: Failed to fetch
The $ref I am using is a full URL with hostname, but I would expect the plugin to lookup the reference using AJV where it is registered, instead of attempting to fetch. Perhaps this is the wrong expectation?
The text was updated successfully, but these errors were encountered:
References are not well supported in 2.x.x, they will be supported in v3. However refs containing full will not likely will be supported, unless you manually create routes where swagger ui could access them via url.
I originally thought this might be related to #30, however I now do not think it is.
I'm using Fastify v2.14.1, and I instantiate my own AJV and configure it using .addSchema(...). I then use the $id references from my manually loaded schemas when creating my route schemas. This works fine in Fastify, and I can tell the schemas are being validated at runtime.
However, when using the plugin UI, and navigating into a particular route, I get the following error, when the schema reference is attempted to be resolved.
The $ref I am using is a full URL with hostname, but I would expect the plugin to lookup the reference using AJV where it is registered, instead of attempting to fetch. Perhaps this is the wrong expectation?
The text was updated successfully, but these errors were encountered: