Skip to content

chore(notif-platform): Allow headers + footers to support rich text#118573

Draft
leeandher wants to merge 7 commits into
masterfrom
leanderrodrigues/iswf-2917-replace-button-for-issue-alert-with-footer-link
Draft

chore(notif-platform): Allow headers + footers to support rich text#118573
leeandher wants to merge 7 commits into
masterfrom
leanderrodrigues/iswf-2917-replace-button-for-issue-alert-with-footer-link

Conversation

@leeandher

Copy link
Copy Markdown
Member

The type has been changed from str to str | list[FormattingBlock], and added pathways for parsing and interpreting both. It seemed to work fine for all providers except I couldn't test MS Teams.

The only caveat is email subjects which obviously can't support rich text.

This approach is kinda ugly but would avoid custom renderers for small adjustments.

@linear-code

linear-code Bot commented Jun 26, 2026

Copy link
Copy Markdown

ISWF-2917

@github-actions github-actions Bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels Jun 26, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

@Christinarlong Christinarlong left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oof that's annoying , I wonder if we can ask claude to do a pass over to change all the current footers to be in the block formatting instead of having to handle both cases

Comment thread src/sentry/notifications/platform/api/endpoints/internal_registered_templates.py Outdated
Comment thread src/sentry/notifications/platform/email/provider.py Outdated
@leeandher leeandher force-pushed the leanderrodrigues/iswf-2917-replace-button-for-issue-alert-with-footer-link branch from 5ee44ae to b5b153e Compare June 26, 2026 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants