refactor(email): use setter method instead AR callbacks
What does this MR do?
This MR removes AR before_validation callback in favor setter.
Are there points in the code the reviewer needs to double check?
No
Why was this MR needed?
Because setters it`s good practice to normalize model attributes instead AR callbacks. Because new object should be valid right after initialization. If it MR interested I can try to find other places where we can use setters.
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
CHANGELOG entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together