Dmitry Dygalo
Dmitry Dygalo
I'd like to have it in `css-inline` and this year sounds realistic to me :) Non-blocking resolving is at the top of my to-do list, but after that, I'd be...
Forgot about the XML part :( Maybe a better way to solve the task described in the original message would be: - A way to configure the underlying parser, currently,...
So, for HTML it would be a different thing that should be integrated into the current inlining process
Let me know if there is anything I can do to help with moving this forward :)
I am thinking about moving the internal state of `CompiledCustomKeywordValidator` to the inner validator, so if they are not needed, the user may choose to keep the overall structure smaller,...
I have an idea how what the API could look like: ```rust #[derive(Debug)] struct AsciiKeyword { size: usize } impl jsonschema::CustomKeyword for AsciiKeyword { fn is_valid(&self, instance: &Value) -> bool...
I'll push some changes to make things work with the API I described above, though there is still enough room to adjust compilation / is_valid / validate signatures so that...
I'll add some more changes soon! Here are a few observations: - Some logic should be moved to the "build" phase, so as soon as we know that the schema...
**Update**: There are not that many things left: - [x] Tune privacy of some types (`InstancePath`) - [x] Update docs (missing docs + doctests) - [x] Tests for schema errors...
I think it is ready to merge! From what I see it should be possible to implement all the cases mentioned in different issues: - Original cases in this PR...