Forms
: Attachment size based functionality restrictions
#518
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.
Related to issue: #apollo/775, #apollo/768
Description:
Restricts rename/delete for empty attachment. This is because rename/delete on an 0 sized attachment will result in error when
applyEdits()
is called.Blocks download and rename of large attachments of > 50 MB. This is because renaming an attachment will load the attachment into memory which we are trying to avoid
Summary of changes:
FormAttachmentState.maxAttachmentSize
specifies the max allowed attachment size that can be loaded. This is 50 MB currently.FormAttachmentState
.AttachmentSizeLimitExceededException
- indicates attachment size exceeds the maximum limit.EmptyAttachmentException
- indicates attachment size is 0.AttachmentTile
can now collect on theFormAttachmentState.loadStatus
to listen to failures and display a toast accordingly.FormAttachmentState.maxAttachmentSize
Pre-merge Checklist