Separated TimeTracker
#17
Merged
Conversation
This file contains 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
|
@ilijamt do you mind rebasing with master so the build can run again? |
…acker` so if we want we don't need to add Created and Deleted properties in the document
ilijamt
force-pushed
the
separate-time-tracker
branch
from
49c38a0
to
0227a7f
Compare
|
@securingsincity Done. |
|
@securingsincity Any reason why they shouldn't be separated? |
|
@ilijamt Thanks! I just wanted to take another look at it. It's on master now. |
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.
Separated
TimeTrackerintoTimeCreatedTrackerandTimeModifiedTrackerso if we want we don't need to add Created and Deleted properties in the document.Now we can implement each field separately and the it's still backward compatible