Comments

fago created an issue. See original summary.

fago’s picture

fago
Primary language German
Location Vienna
CreditAttribution: fago at drunomics commented

klausi, do you have some thoughts on how to handle langcode/translation during data fetching?
no, i have ignored that so far
klausi, so far, we have one $langcode parameter and try to apply it for everything that is translatable. But I'm wondering whether it wouldn't be better to move to some more explicit variant, ala node:en:title - as sometimes you might not want to apply the langcode everywhere possible
klausi, e.g. consider, node:field_reference:entity:title:value - you might want to translate entity 1, but not entity 2 ?

dasjo’s picture

dasjo
he/him
Primary language German
Location Zurich
CreditAttribution: dasjo as a volunteer and at Amazee Labs commented
Parent issue: » #2632564: [META] Rules Twig-style Token support
TR’s picture

TR CreditAttribution: TR commented
Project: Rules » Typed Data API enhancements
Version: 8.x-3.x-dev » 8.x-1.x-dev
Component: Rules Core » Placeholderresolver

Should probably figure out how to do this within Typed Data API Enhancements. Could just always use the current user's language, but allow that to be overridden by a data filter for situations like when you want to send mail in the recipient's language.

fago’s picture

fago
Primary language German
Location Vienna
CreditAttribution: fago at drunomics commented

When discussed with fubhy, we had the idea of supporting @syntax for transformers like that. So we could have entity@languag('de').field etc. ?

TR’s picture

TR CreditAttribution: TR commented
Version: 8.x-1.x-dev » 2.0.x-dev