Repository navigation
Conversation
SendEmailParams only described to/subject/body/from_name, and called body plain text when it has always been sent as HTML. The backend also accepts html (the same slot as body), text (a plain-text part, alone or alongside the HTML) and attachments, so body is now optional. SendEmailParams stays a plain interface: an "at least one of" mapped type makes TypeDoc drop the whole property list from the Mintlify page. Template fields (template_id, template_name, variables, category) stay out while email templates are in preview. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
🚀 Package Preview Available!Install this PR's preview build with npm: npm i @base44-preview/sdk@0.8.59-pr.370.a3fc0aePrefer not to change any import paths? Install using npm alias so your code still imports npm i "@base44/sdk@npm:@base44-preview/sdk@0.8.59-pr.370.a3fc0ae"Or add it to your {
"dependencies": {
"@base44/sdk": "npm:@base44-preview/sdk@0.8.59-pr.370.a3fc0ae"
}
}
Preview published to npm registry — try new features instantly! |
…chment
Inside a field, the docs pipeline drops {@link} and code formatting,
so link UploadFile() and UploadPrivateFile() to their sections with
markdown anchors. Rephrase "Supported extensions:" so it isn't a
colon used as a sentence break.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Summary
Brings
SendEmailParamsin line with whatCore.SendEmailaccepts. The current docs only listto,subject,bodyandfrom_name, and they describebodyas plain text, but it has always been sent as HTML.html: the same slot asbodyunder an explicit name. Set one or the other.text: a plain-text part. It works alone, or alongsidebody/htmlto send both versions in one email.attachments: up to 5 files, either a file the app uploaded (file_url) or base64content. Exported asEmailAttachment.bodyis now optional. Existing callers still compile.SendEmail()docs now say who you can email, and have two examples.Types and docs only. The integrations proxy already posts whatever object it gets, so these fields already reach the backend.
This replaces #266 (opened from a fork) and ports it to
packages/sdk. Changes from #266:SendEmailParamsstays a plain interface. With feat(types): add html and text fields to SendEmailParams #266'sRequireAtLeastOne<…>alias, TypeDoc drops the whole property list from theSendEmail()section of the Mintlify page. The "at least one ofbody,htmlortext" rule is in the parameter description instead.Template fields (
template_id,template_name,variables,category) stay out while email templates are in preview.Test plan
npm test -w @base44/sdk: type tests and 437 unit tests passnpm run lintnpm run create-docs: theSendEmail()section lists every field, including the nestedattachmentsproperties, and both examples render🤖 Generated with Claude Code