-
-
Notifications
You must be signed in to change notification settings - Fork 285
refactor: create nextOccurrence
and nextOccurrenceDate
methods in Occurrence
#2983
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: create nextOccurrence
and nextOccurrenceDate
methods in Occurrence
#2983
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(I had a longer version of this message but lost the edit...)
I like where this is going.
Any thoughts on Occurrence.ts
though?
And also Occurrence.test.ts
?
Ofc! Extracted in a later commit/PR |
I did some work on this but not much since changing a line of code in current Maybe we can quickly discuss ways to improve the tests on our next session when all the PRs are merged. |
Great - thanks. |
Just to clarify, I meant that we/I would do it later, after the refactoring is done, since the code being refactored is covered by tests. So would be good if you find some time to review/approve/merge of this PR =) |
Understood - am really busy at the moment... But OK, will do it now... |
Thanks! |
Merging un-reviewed - please add 'internal' and 'recurring' labels to this and any recent closed ones that I forgot to do this... |
Done! |
Types of changes
Internal changes:
refactor
- non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)test
- additions and improvements to unit tests and the smoke tests)Description
Occurrence
-related behaviour toOccurrence
classMotivation and Context
How has this been tested?
Checklist
yarn run lint
.Terms