The following filter function was chosen to prevent possible side effects of changing the order of the predicates list.
val isObituary: ContentFilter = content => (tagExistsWithId("tone/obituaries")(content) && !tagExistsWithId("tone/letters")(content))
However we could not find any articles that shared the tags in the hierarchy between obituaries and letters and simply changing the order may be a better more implicit implementation.
@DanielCliftonGuardian @AshCorr @ioannakok was this released independently or did it go out as part of the 19.0.4 version that @alinaboghiu and @rowannekabalan released?
Co-Authored-By: Ashleigh Carr ashcorr20@gmail.com Co-Authored-By: Ioanna Kokkini ioannakok@users.noreply.github.com
What does this change?
This change renders obituary letters as letters and resolves issue https://github.com/guardian/dotcom-rendering/issues/5628.
Have we considered potential risks?
The following filter function was chosen to prevent possible side effects of changing the order of the predicates list.
val isObituary: ContentFilter = content => (tagExistsWithId("tone/obituaries")(content) && !tagExistsWithId("tone/letters")(content))
However we could not find any articles that shared the tags in the hierarchy between obituaries and letters and simply changing the order may be a better more implicit implementation.
Images