Skip to content
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

Support joi v16 #3975

Closed
hueniverse opened this issue Sep 15, 2019 · 2 comments

Comments

@hueniverse
Copy link
Member

commented Sep 15, 2019

No description provided.

@hueniverse hueniverse added the feature label Sep 15, 2019
@hueniverse hueniverse added this to the 18.4.0 milestone Sep 15, 2019
@hueniverse hueniverse self-assigned this Sep 15, 2019
@kanongil

This comment has been minimized.

Copy link
Member

commented Sep 15, 2019

There will still be issues with the fix when composing. Eg. for:

validate: {
    payload: {
        a: JoiNext.number(),
        b: JoiNext.array()
    })
}

So some care has to be taken to use a Joi object as the top-level option.

@Marsup

This comment has been minimized.

Copy link
Member

commented Sep 15, 2019

As explained here: hapijs/joi#2107 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.