Skip to content
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

feat(domains) Add utility methods to unblock email updates #42175

Merged
merged 2 commits into from Dec 12, 2022

Conversation

markstory
Copy link
Member

We need to update all the links embedded in emails to reflect customer domains. I didn't want to add conditional branching to all the emails, so instead I've added a few more utility methods to Organization so that help generate absolute URLs for an organization.

In order to generate URLs correctly for customer-domains I needed to port the URL replacement logic we use in the frontend to the server as well.

We need to update all the links embedded in emails to reflect customer
domains. I didn't want to add conditional branching to all the emails,
so instead I've added a few more utility methods to `Organization` so
that help generate absolute URLs for an organization.

In order to generate URLs correctly for customer-domains I needed to
port the URL replacement logic we use in the frontend to the server as
well.
@markstory markstory requested a review from a team December 8, 2022 20:25
@markstory markstory requested review from a team as code owners December 8, 2022 20:25
@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 Dec 8, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2022

🚨 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.

@markstory markstory merged commit 2f4e19c into master Dec 12, 2022
@markstory markstory deleted the issue-link-domains branch December 12, 2022 14:51
@github-actions github-actions bot locked and limited conversation to collaborators Dec 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.

None yet

2 participants