Ensure matching 'modified' and 'creation' collection values on create #40
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
griffri
force-pushed
the
fix/new_collection_timestamps
branch
from
3f8add6
to
af14782
Compare
griffri
changed the title
|
Is it worth modifying a test to check these values are the same on POST? |
…he `created` and `modified` values are the same
griffri
force-pushed
the
fix/new_collection_timestamps
branch
from
72cd932
to
134d39d
Compare
JackLewis-digirati
approved these changes
Sep 23, 2024
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.
Resolves #39
This PR fixes a minor bug that caused a slight difference between the
createdandmodifiedtimestamps on a newly created collection, caused by callingDateTime.UtcNowtwice.