Refactor hard-coded email messages as template files #149
Assignees
Comments
|
This is a good idea, I had this same feeling writing the code before. |
lilliputten
added a commit
to lilliputten/dds_registration
that referenced
this issue
Apr 10, 2024
lilliputten
added a commit
to lilliputten/dds_registration
that referenced
this issue
Apr 10, 2024
…gress): passing request parameter to message generation code, added templates for payment invoice, added email helpers.
lilliputten
added a commit
to lilliputten/dds_registration
that referenced
this issue
Apr 10, 2024
lilliputten
added a commit
to lilliputten/dds_registration
that referenced
this issue
Apr 10, 2024
…currencies list from constants instead of literal list, with missed 'USD' value).
lilliputten
added a commit
to lilliputten/dds_registration
that referenced
this issue
Apr 10, 2024
lilliputten
added a commit
to lilliputten/dds_registration
that referenced
this issue
Apr 10, 2024
…egistration invoice event. Cleaned up code.
lilliputten
added a commit
to lilliputten/dds_registration
that referenced
this issue
Apr 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
All email texts and subjects are hard-coded in the
dds_registration/models.py.Unless it was done on purpose, they should be refactored in a form of standalone templates (probably with substitutable variables for names, urls, emails).
The text was updated successfully, but these errors were encountered: