-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested refs not resolved correctly when schema supplied as string #446
Comments
Hi, which version are you using? (or are you using the web app?) There was an issue like this fixed recently. |
This is the web site |
I think you're hitting #250. This should be fixed when I update the site to the latest version. Thanks for reporting this. |
Ok - I'll keep my eye out for it. Thanks! |
I've updated the site to the latest plugin version (0.4.16) so you should be good to go. I've tested your schema and seen some generated output. |
Ok, it seems that while it does seem to generate types for the schema above, it runs into a different (?) problem with the schema below. The error I'm getting from the site is:
|
For reference, I can drop that schema here with the object below, and it parses the schema and validates the object without error, so I don't think the problem is in the schema definition itself:
|
Thanks for the update. I've had a look into this and I can definitely see a problem. It relates to how nested refs are resolved when there is no file but just a string given directly to the plugin (this is how the website works). I've resolved this using your example so it will be released in the next version. Cheers |
ok - thanks! |
This schema fails with "URI is not absolute":
The text was updated successfully, but these errors were encountered: