[10.x] Fix custom themes not reseting on Markdown renderer #46200
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes the issue described in #46179. It should reset the theme to
'default'
on the Markdown renderer object if no$theme
is set on theMailable
object. I've also added a test for this. This PR does not introduce any breaking changes.There's a small inconsistency between
Mailable
andMarkdown
classes, theMailable
class has a default$theme
value ofnull
(implicitly the default theme), howeverMarkdown
has a default theme value of'default'
(here and here). But fixing this inconsistency might be a breaking change, so not sure if you'd want to fix it.