-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
validate_file
is a no-op because valico
isn't compatible with serde
1.0
#11
Comments
Notes: - `valico` is not currently usable without extra hacks. See #11 and s-panferov/valico#27 - `regex` has some API changes. - `serde` has massive API changes. - `error-chain` isn't worth the trouble of updating; we'll just switch over to `failure` sometime soon. CC @seamusabshere @camjackson
@camjackson We can certainly just disable this warning. The lack of valico means that we probably have worse error messages, and we don't validate inputs and outputs as well as we should. The real fix is to get a version of valico with the fixes mentioned above merged (and ditto for a second crate used by valico). At this point, that probably means forking both libraries and releasing them to crates.io. There's also a trick we could do by releasing a single shim library that re-exports the older serde APIs (And serde JSON?) under a new name. Probably the first step would be to ping upstream more aggressively. But in the meantime, we can turn this warning off or replace it by |
This is the nature of open source I guess! As an end user, I think it would be best if Cage didn't log the extra information. It's quite noisy to have it there on every cage command, especially multiple times per command. But I also see the value in having something there in the code as a reminder that the validation function is a noop. Would a |
A On the other hand, this is actually a real So, choices:
But the problem with (3) is that once we start releasing shim crates, why not just fork the crates we actually need and update them? I can't find any other JSON Schema implementations in Rust at the moment. |
That all makes sense. Maybe let's put this on hold for a short while, giving upstream developers a chance to respond. And if they don't have bandwidth then we can consider the options further. |
The
validate_file
function incompose_yml
is supposed to make sure that all the files we read and write correspond to an appropriate JSON schema. Unfortunately, this relies onvalico
, which appears to be currently unmaintained, and which only works withserde
0.8.See s-panferov/valico#27 for a PR that would fix this.
The text was updated successfully, but these errors were encountered: