This repository has been archived by the owner on Oct 2, 2019. It is now read-only.
The Contact constructor should not set id / lastUpdated attributes #60
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
The Contact constructor should not set id / lastUpdated attributes. Those should be initially null and generate asynchronously by the call to ContactManager.save() because this is when the implementation actually interacts with the database. The specification actually already states that the save() method will set the id and lastUpdated attributes on the contact that is asynchronously returned. This issue was reported by Huang Deqing <[email protected]>.
|
Any update on this? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The Contact constructor should not set id / lastUpdated attributes. Those should be
initially null and generate asynchronously by the call to ContactManager.save()
because this is when the implementation actually interacts with the database. The
specification actually already states that the save() method will set the id and
lastUpdated attributes on the contact that is asynchronously returned.
This issue was reported by Huang Deqing [email protected].