#159222976 Add id nonce to ensure new entry Id uniqueness #12
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.
What does this PR do?
Fixes bug that results from deleting an entry and adding a new entry in the previous build. Adding a new entry after a deletion results in entries with the same ids. This bug has been corrected with the use of an id nonce for generating ids for new entries.
Description of Task to be completed
How should this be manually tested?
API endpoint has been deployed to: https://my-diary-api.herokuapp.com/api/v1
Using Postman:
/entries
to retrieve a list of all available entries/entries/:id
for one of the available entries/entries
with body{ "timestamp": 153462783, "title": "title", "content": "content", "isFavorite": true }
What are the relevant pivotal tracker stories?
#159222976