Handle non-integer and empty meetings#39
Merged
Marsup merged 1 commit intohapijs:masterfrom Aug 21, 2025
Merged
Conversation
damusix
approved these changes
Aug 21, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a bugfix to handle weird values for meetings, that could happen in user code when it is a computed or derived value. Any value that now throws would have unexpected behaviour.
This also includes a minor new feature, which is the handling of
{ meetings: 0 }withoutstrict. In this case, it will immediately resolve the meeting with anullvalue. Previously, it would behave as{ meetings: 1 }, which seems quite wrong.