Skip to content

fix: correct typo in notification template #14108

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

Merged
merged 1 commit into from
Aug 2, 2024
Merged

Conversation

mtojek
Copy link
Member

@mtojek mtojek commented Aug 2, 2024

Related: #14010

There is a typo in the notification template, unescaped character.

@mtojek mtojek self-assigned this Aug 2, 2024
@mtojek mtojek changed the title fix: typo in notification template fix: correct typo in notification template Aug 2, 2024
@mtojek mtojek requested a review from dannykopping August 2, 2024 07:57
@mtojek mtojek marked this pull request as ready for review August 2, 2024 07:57
@@ -0,0 +1,5 @@
UPDATE notification_templates
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't really see value in restoring the typo in the down migration.

Copy link
Member Author

Choose a reason for hiding this comment

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

just consistency?

@@ -0,0 +1,5 @@
UPDATE notification_templates
SET
body_template = E'Hi {{.UserName}},\n\nNew user account **{{.Labels.created_account_name}}** has been created.'
Copy link
Contributor

Choose a reason for hiding this comment

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

This was incorrectly set in the initial migration, let's sneak it in here if you don't mind

Suggested change
body_template = E'Hi {{.UserName}},\n\nNew user account **{{.Labels.created_account_name}}** has been created.'
body_template = E'Hi {{.UserName}},\n\nNew user account **{{.Labels.created_account_name}}** has been created.',
group = 'User Events'

Copy link
Member Author

Choose a reason for hiding this comment

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

I would rather keep this idempotent. It does not seem to be an urgent fix that requires modifying existing files, and if there are some scripts checking the content of migration files, and I wouldn't like to make them suffer.

Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe you missed the content of the change? The event is a user event, but its group is incorrectly set to Workspace Events currently.

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh crap, let me redo it.

Copy link
Member Author

Choose a reason for hiding this comment

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

@mtojek mtojek merged commit 76ce460 into main Aug 2, 2024
32 checks passed
@mtojek mtojek deleted the 17-fix-user-created branch August 2, 2024 09:03
@github-actions github-actions bot locked and limited conversation to collaborators Aug 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants