-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding cypress test for new attachment API + fixes #2821
Conversation
…nstance data, the attachments should be considered to be deleted.
…t in the node hierarchy. This makes sure we also update the IDs if an attachment is deleted on the backend (when the backend aldo doesn't update that field in the data model).
…, as attachments don't always map themselves when added to the instance data.
Quality Gate failedFailed conditions |
* If the attachment is deleted from the instance data outside of these functions (i.e. by a backend hook), these | ||
* components will make sure to remove the attachment ID from the data model: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, I did not think of this case 🥇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice!
Description
When I tested the functionality implemented in #2754, I found two problems:
useNodeAttachments()
that carries over previously-seen attachments also did that for successful uploads, but the comment indicated it was only supposed to happen for uploads in progress.Maintain*DataModelBinding
components to make sure we update those values when instance data elements disappear.Also adding a cypress test for this functionality, with a somewhat hidden test structure and quite strange
IDataWriteProcessor
in thettd/subform
app.Related Issue(s)
Verification/QA
kind/*
label to this PR for proper release notes grouping