This repository has been archived by the owner on May 14, 2024. It is now read-only.
prevent metadata value from getting cached #494
Merged
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.
Description
so when a property object is assigned to another object, it creates a shallow copy and hence when I edited the
extractedMetadata.creationTime
, it also edited the creation time on theNULL_EXTRACTED_METADATA
too which was used to initialise itfixed it by not editing the value, instead of adding a fallback to the initialisation of creationTime in the response object
Test Plan
tested locally by trying to upload multiple files with no EXIF data but having DateTime in the filename so that the issue would get triggered but it didn't occur. All is good