Skip to content

feat(tasks)!: support custom assignment email on task create - #43

Merged
priosshrsth merged 1 commit into
mainfrom
feat/task-assignment-email
Sep 28, 2026
Merged

priosshrsth merged 1 commit into
mainfrom
feat/task-assignment-email

Conversation

@priosshrsth

Copy link
Copy Markdown
Collaborator

Adds an optional email to tasks.create() that replaces the default assignment email (subject, header, title, body/htmlBody, ctaParams), matching what mys-dashboard already sends to POST /v1/tasks. Also fixes the task schema, which used field names the API doesn't have.

Breaking: title → name; assigneeId/assigneeType → internalUserId/clientId/companyId. Releases as 0.1.0.

What to look at:

  • src/lib/modules/tasks/schema.ts: the email field isn't in the public OpenAPI spec. Its shape comes from mys-dashboard's working call; body and ctaParams are borrowed from the notification email shape and not yet exercised.
  • Response Task still requires createdAt, per the OpenAPI spec; the docs' example object shows createdDate instead.

Verified: vp check and unit tests (new test asserts the email is forwarded in the body). Not verified against the live API.

🤖 Generated with Claude Code

The task request and response types now use the API's field names.

BREAKING CHANGE: task `title` is now `name`, and `assigneeId`/`assigneeType`
are replaced by `internalUserId`, `clientId` and `companyId`.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@priosshrsth
priosshrsth merged commit 79079d8 into main Sep 28, 2026
5 checks passed
@priosshrsth
priosshrsth deleted the feat/task-assignment-email branch September 28, 2026 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant