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.

Sign up for GitHub

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

Jump to bottom

{ result, error } changed to error undefined instead of null #2036

Closed
hueniverse opened this issue Aug 10, 2019 · 0 comments
Closed

{ result, error } changed to error undefined instead of null #2036

hueniverse opened this issue Aug 10, 2019 · 0 comments
Assignees
@hueniverse
Labels
breaking changes Change that can breaking existing code
Milestone
16.0.0

Comments

@hueniverse
Copy link
Contributor

No description provided.

@hueniverse hueniverse added the breaking changes Change that can breaking existing code label Aug 10, 2019
@hueniverse hueniverse added this to the 16.0.0 milestone Aug 10, 2019
@hueniverse hueniverse self-assigned this Aug 10, 2019
@hueniverse hueniverse added the v16 label Aug 11, 2019
@hueniverse hueniverse mentioned this issue Aug 11, 2019
Closed
@alxtsg alxtsg mentioned this issue Oct 2, 2019
Closed
@tdukai tdukai mentioned this issue Jan 14, 2020
Closed
romankaravia added a commit to nzzdev/Q-server that referenced this issue Feb 7, 2020
@romankaravia
Update dependencies and adapt code
54ef376 
Summary of relevant changes

@hapi/joi v16
- Changes in allow() and valid()
  No longer accepts array arguments. Must pass each value as a separate argument.
  See hapijs/joi#2037
- Change error in sync validate() result to undefined instead of null when there is no error
  See hapijs/joi#2036
  See hapijs/joi#2037

@hapi/hapi v19
  - No joi schema compiler is loaded by default and must be explicitly
  loaded using server.validator()
  See hapijs/hapi#4017
  See https://hapi.dev/api/?v=19.1.0#-servervalidatorvalidator

@hapi/boom v8
  - Change new Boom() to new Boom.Boom()
  See hapijs/boom#253
@lock lock bot locked as resolved and limited conversation to collaborators Feb 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@hueniverse hueniverse

Labels
breaking changes Change that can breaking existing code
Projects
None yet
Milestone
16.0.0
Development

No branches or pull requests
1 participant
@hueniverse