Repository navigation
fix: delete availability when no time slots are defined - #65594
Open
SebastianKrupinski wants to merge 1 commit into
Open
SebastianKrupinski wants to merge 1 commit into
SebastianKrupinski wants to merge 1 commit into
Conversation
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
SebastianKrupinski
requested review from
pringelmann
and removed request for
a team
October 16, 2026 21:10
SebastianKrupinski
requested review from
ChristophWurst,
DerDreschner,
GVodyanov,
kesselb and
odzhychko
October 16, 2026 21:11
Contributor
Author
|
/backport to stable35 |
Contributor
Author
|
/backport to stable34 |
Contributor
Author
|
/backport to stable33 |
This branch has not been deployed
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
1 participant
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.
Summary
Resolves: # Internal ticket
Previously when no time slot where defined we would save the availability with an empty VAVAILABILITY block but according to the RFC 7953 and empty block means that the user is an available all the time. So instead of saving an empty block we should delete the property when no slots are defined.
Checklist
3. to review, feature component)stable32)AI (if applicable)