Set access to 1 on new calendars to handle share with null #1581
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.
When a new calendar is created via DAV or from the iOS calendar app a "empty" shared user (null) is always created.
Apparently the iOS calendar app assumes to have a shared-owner calendar even when the calendar is not shared.
see sabre-io/Baikal#1090
This PR sets the access value for new calendars to '1' like it is already done in baikal