-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
"Describe" behavior changes for "implicit" Any with extended Joi #1067
Comments
I'm currently looking into this, but wanted to submit the issue in the meantime in case anyone has input on the issue :) |
It looks like |
Ok, it looks like it may just be too bad. When But! When I'm going to leave this open for visibility and just in case I misunderstood something, but I think it is a dead end without re-implementing |
Closing this out now. Not sure why I felt the need to leave it open for so long. |
I'm not sure what to do with this, this is definitely a bug, but I don't yet see a way out of it. |
OK, found a way, never talk too soon :) |
Oh, nice! :D I couldn't find a way out of it either. My only "solution" was essentially a breaking change rewrite of how |
It doesn't seem to break anything but who knows :D |
Context
What are you trying to achieve or the steps to reproduce ?
I know that using
Joi.any().valid('value')
is preferable over usingJoi.valid('value')
, but the behavior of.describe()
is changing between the two cases when Joi is extended.This change in
describe
is less than ideal for Felicity since we built off ofdescribe()
and hope to support extensions soon.I'm using joi-date-extensions here, but it appears to be related to
.extend
rather than the extension itself.The text was updated successfully, but these errors were encountered: