saved_changes method behaves differently on staging server and on loc… #1083
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.
…al server. Hence added explicit check to check newly created record
Purpose
datacite/datacite#1710
Saved_changes
rails method gives incorrect result on staging server, ideally for newly created record it should give whole object, as there was no record before. Hence I have added a condition to check newly created record.This is the staging server response for
saved_changes
Locally we get whole changes of that object, see the log below
I have done the testing for following cases on staging,