#9583 Fix SaveAs plugin showing persisted data #9984
Merged
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
Added unadvertised field in Metadata.jsx, shown in modal form. Checkbox, controlled. Adjust handleResourceData.jsx enhancer, include unadvertised field from resource originalData unto props passed to Metadata.jsx. Added translations for unadvertised field.
…r, created, lastUpdate and advertised are now removed and will not be shown / default to unspecified.
Igi-ID
added
New Feature
Closed
6 tasks
offtherailz
approved these changes
Feb 21, 2024
|
@ElenaGallo, could you please test this on DEV, as well as it is merged and deployed ? Thank you |
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.
Description
This PR introduces a fix for the SaveAs plugin showing persisted resource metadata in the modal fields, while the plugin itself is used to create a new resource. Fields such as creator, editor, created, lastUpdate are now omitted and advertised reverts to default.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
Reported issue
#
What is the new behavior?
Fields are not shown, as mentioned in the description.
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information