-
Notifications
You must be signed in to change notification settings - Fork 422
fix(firestore-send-email): improve attachments validation error message #2583
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
Open
HassanBahati
wants to merge
8
commits into
next
Choose a base branch
from
@invertase/fix/firestore-send-email-improve-attachments-error-message
base: next
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
fix(firestore-send-email): improve attachments validation error message #2583
HassanBahati
wants to merge
8
commits into
next
from
@invertase/fix/firestore-send-email-improve-attachments-error-message
Conversation
This file contains hidden or 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
…onStart event (#2562) * fix(storage-resize-images): add missing recordStartEvent call * feat(storage-resize-images): add onStorageResize event * docs(storage-resize-images): update changelog * chore(storage-resize-images): add onStartResize * chore(storage-resize-images): add onStartResize event --------- Co-authored-by: Tadej <[email protected]>
cabljac
reviewed
Jan 12, 2026
cabljac
reviewed
Jan 12, 2026
| if (issue.message && !issue.message.startsWith("Expected")) { | ||
| return issue.message; | ||
| } | ||
|
|
Contributor
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.
Actually i think a cleaner fix is I think in here we need
case "invalid_type":
// Missing required field (received undefined)
if (issue.received === "undefined") {
return `Field '${path}' must be a ${issue.expected}`;
}
// Type mismatch cases
if (issue.expected === "string") {
return `Field '${path}' must be a string`;
}
if (issue.expected === "array") {
return `Field '${path}' must be an array`;
}
Contributor
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.
@HassanBahati did you push changes taking this approach? i dont see them
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.
Fixes #2550 (comment)
Adds a custom error message to attachmentsSchema when an object is provided instead of an array. The new message guides users to wrap single attachment objects in an array format.