Jonas Schmidt

Yes, that sounds like a requirement that should be covered somehow. I like the idea of including the fragment in the error struct, but the issue could be that the...

After trying out a few things, I think it might be better to include the current fragment in the `%ExJsonSchema.Validator.Error{}` struct like you proposed. There's a [branch](https://github.com/jonasschmidt/ex_json_schema/tree/errors-with-fragments) where I had...

Ok, maybe just open a PR so I can have a look at the proposed changes. Adding more context to the fragment would definitely be more work, because the outer...

Hey, so I don't really get the use case for this. The draft schemas are bundled in the lib and will not be fetched over the network. Why would you...

Yes, good point. There were some breaking changes from `0.5.x` to `0.6.0`, mostly resulting from functions that were intended for internal use being used as public API because there was...

Thanks for reporting this, I will have to look into it. To be honest, the whole part about using ids to change the resolution scope and referencing to them is...

Yes, absolutely. The main hurdle could be the changed behavior around references. Some things have been simplified/clarified, so it might not be that bad, but I haven't had a chance...

Ok, some update about the progress. When looking into the new features in the 2019/2020 drafts I realized that there is no point in working on those before properly adding...

Hey, I'm afraid I haven't made much progress since February, no time to work on it. There's a [branch](https://github.com/jonasschmidt/ex_json_schema/tree/draft-2020-12) with my work so far if you want to have a...

Hey, you can provide a custom format validator to handle non-standard formats. There's a section in the README explaining how to do that: https://github.com/jonasschmidt/ex_json_schema?tab=readme-ov-file#custom-formats