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

Fix/4274 write nicer html emails #4274 #4410

Conversation

RAISEMEUP007
Copy link
Contributor

No description provided.

@vercel
Copy link

vercel bot commented Jun 5, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
dao ✅ Ready (Inspect) Visit Preview Jun 14, 2023 6:26am
pioneer-2 ✅ Ready (Inspect) Visit Preview Jun 14, 2023 6:26am
pioneer-2-storybook ✅ Ready (Inspect) Visit Preview Jun 14, 2023 6:26am

</ModalHeader>
<ModalContent>
<ContentTitle>Hi {'{name}'},</ContentTitle>
<ContentBody>New proposal {'{proposal name}'} is created... there are 2 days left to vote...</ContentBody>
Copy link
Contributor

Choose a reason for hiding this comment

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

According to the issue #4274
you must create six variations of notifications. Please create the text of the contentbody and button as variables.

Copy link
Contributor

@chrlschwb chrlschwb left a comment

Choose a reason for hiding this comment

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

You must define "EmailNotifications.tsx" inside "src/common"

setShowModal(true)
}
const openModal280 = () => {
setShowModal280(true)
Copy link
Contributor

Choose a reason for hiding this comment

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

this value must be defined as content variable, not state variable

Copy link
Member

@thesan thesan left a comment

Choose a reason for hiding this comment

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

@AnttoLion I don't know if this PR is still in progress, but in case it is:

Using React to generate html emails looks like a bad idea. Remember that the emails are generated on the backend so there shouldn't be any changes in packages/ui/*. Also you can't run js in emails and even though React can be used for ssr it's really not the right tool when the frontend can't run React.

@kdembler
Copy link
Member

kdembler commented Sep 3, 2023

@thesan This is superseded by my PR, can be closed

@thesan
Copy link
Member

thesan commented Sep 8, 2023

Done in #4511

@thesan thesan closed this Sep 8, 2023
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.

5 participants