JsonSchema.FromFile sets BaseUri incorrectly about json-everything HOT 5 CLOSED

I'm pushing out v1.5.1. Please close if that resolves this issue for you.

from json-everything.

I'm going to have to do some research on file-based URIs before I do anything. I'll post relevant links here.

from json-everything.

This blog post seems quite pertinent. It's the first thing I found, and he does what I'm doing.

However, playing with your fiddle and his, using both Linux and Windows yield an absolute URI without the file:/// scheme, as you suggest. But his doesn't work with Linux paths.

I was also surprised to find that /home/path.json is an absolute path.

Another thing the blog gets right that I should consider is that the path needs to not be URL-encoded since the system will attempt to re-encode it. I think this is something that I'll just add to the docs rather than try to force.

from json-everything.

Works in my case, please consider adding baseUri to FromText and FromStream as well, it could be used if fetching schema from the web (in case it doesn't use $id) or from other sources (resource or an archive).

from json-everything.

I think I'm going to leave the other two as they are. The options expose a DefaultBaseUri now.

from json-everything.