Repository navigation
0.3.0-rc.18: moved native recurring occurrences keep their identity in calendar projection - #23
Merged
Merged
Conversation
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
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.
Adds
recurrence_original_dateto the model and the calendar module, matching TaskNotes plugin #2396: a moved next occurrence renders only at its new date, keeps its original identity for ids, completion/skip and materialized-child suppression, and calendar edit plans capture, preserve or clear the marker. 11 new shared calendar fixtures.Verified locally:
npm test(109),npm run typecheck,npm run test:package.