Merged
Conversation
Contributor
Author
|
@edalzell I've managed to fix the issue by cloning the object while mapping. Later iterations overwrote the supplements, since it was the same object. I'm not sure if this is the right approach, but it works. |
edalzell
force-pushed
the
fix/add-spanning-start-end
branch
from
d1b0f98 to
15e4bc1
Compare
edalzell
approved these changes
Apr 17, 2026
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
2 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 PR adds
spanning_startandspanning_endto the supplements data. Additionally, it removes the legacydateskey from the calendar return values (they were the same asoccurrences).