Julian Berman
Julian Berman
Hey! Sorry it took me so long to get to this, finally back home. That module is... pretty disappointing :/. I'd like to spend a bit of time understanding why...
RefResolver (or its successor) should allow customizing deserialization, not only scheme / retrieval
Have to respond in a bit more length -- something a bit more general than that (that doesn't use file extensions, just fully allows someone to inject in what to...
RefResolver (or its successor) should allow customizing deserialization, not only scheme / retrieval
Not the JSON spec, an *HTTP* spec On Thu, Jun 7, 2018, 13:14 Martin Kelly wrote: > I agree with that ideally being in spec but don't know enough to...
RefResolver (or its successor) should allow customizing deserialization, not only scheme / retrieval
Or a more general URI one On Thu, Jun 7, 2018, 13:19 Julian Berman wrote: > Not the JSON spec, an *HTTP* spec > > On Thu, Jun 7, 2018,...
RefResolver (or its successor) should allow customizing deserialization, not only scheme / retrieval
Still haven't gotten a chance to elaborate here, but just on that last message -- just in case you weren't aware, all JSON is essentially valid YAML.
I'm revisiting this due to having a look at a bunch of tickets surrounding `$ref`, e.g. https://github.com/python-jsonschema/jsonschema/issues/274#issuecomment-1195387858. I'm looking for ways to make this more obvious to people / harder...
Hi, thanks. I *believe* this likely will be a duplicate of #371 (i.e. for location-independent identifier support, which is a known open issue) -- though GitHub closed #371 when I...
No worries! All good -- I do assume though the upstream test suite issue may be closeable, because yeah I think this behavior is likely already covered by the tests...
#371 was closed accidentally when renaming the master branch and GH doesn't allow reopening it. But yes location independent identifiers are a known bug (one of a few -- see...
Hey. There isn't unfortunately. There should be. It just doesn't exist because I haven't thought of a nice way to expose it yet. There's an informal agreement that `.path` and...