however lets try to access the raw resource directly.
It is different from the currently downloaded spec, so I try to replace the link only first.
@zeitlinger@vadeg can you approve.
sorry still fails. :(
Looks like we correctly load the local schema as a JsonNode and then pass that to our JsonSchemaValidator with redirects setup for just http://json-schema.org/draft-04. I think, when validating the local schema internal references are being found and translated into absolute references, but nothing in the underlying validation understands that this is the the local schema that the process is starting from, and loads over http instead. Consequently adding an extra redirect for the originally loaded schema seems to hack around the problem - although I still suspect it means we're unnecessarily loading the original schema multiple times.
Yes, unless a cache in the parser is active to prevent this.
np - was very concerned that i'd caused it with my recent refactoring so was extra motivated to understand - the fix/hack was a bonus
thanks. i role out as quick as possible.
Hello everyone, I have a question regarding adding my own rule. I'm a little lost because I'm not really sure where I should be creating my own rules, and how to know if they are being implemented correctly. Should I just add them in a package on zally/server or is it different from the way zalando/zally rulset are implemented? Also do I have to create a rulset if I want to add a single rule? I'm sorry for all the questions but I can't find much info about it (besides the documentation) or even another project that uses zally (if anyone has an example it would be super useful). I'm checking different ways to validate an api and zally caught my attention. Any help is appreciated, thank you!
Hi. Work to make developing custom rules easier is coming along but still not there yet, so the viable options for now are (1) contribute your new rule to Zally itself or (2) forking the repo and adding private rules to your own fork.