-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
[Mailer][TwigBridge] Add support for translatable subject #59967
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -58,9 +58,9 @@ class Email extends Message | |
/** | ||
* @return $this | ||
*/ | ||
public function subject(string $subject): static | ||
public function subject(string|\Stringable $subject): static | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This may be a breaking change for apps that extend this class and override this method (https://3v4l.org/uuJj9) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Supporting a TranslatableInterface is absolutely not the same than supporting Stringable. There is no requirement for TranslatableInterface to be Stringable. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, my idea was off the cuff. Needs to be thought out more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. btw, even for the core TranslatableMessage (that is stringable), casting it to string does not translate it. It returns the translation key. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right, I thought that'd be fine as that's the behavior of using keys that don't have a translation. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. My thinking was to allow the subject to be any stringable object allowing a listener to intercept. If none does, it would just be cast to a string. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Adding support for Stringable and then doing weird magic to support TranslatableMessage while the changelog says it adds support for translatable subject (which would be understood as being the interface by many people) looks wrong to me (and limiting as there are valid use cases for other implementations of TranslatableInterface) |
||
{ | ||
return $this->setHeaderBody('Text', 'Subject', $subject); | ||
return $this->setHeaderBody('Text', 'Subject', (string) $subject); | ||
} | ||
|
||
public function getSubject(): ?string | ||
|
Uh oh!
There was an error while loading. Please reload this page.