- First commit to issue fork.
- @royalpinto007 opened merge request.
- ๐ฎ๐ณIndia royalpinto007
This commit updates the documentation for the Drupal API page to provide more clarity on accessing the original entity object in a multi-language context. It also suggests alternative methods for retrieving the original translation if $entity->original does not refer to the expected translation. This should help improve understanding for developers working with Drupal in a multi-language context.
- Status changed to Needs review
almost 2 years ago 10:52am 24 February 2023 - Status changed to Needs work
almost 2 years ago 2:08pm 13 March 2023 - ๐บ๐ธUnited States smustgrave
Change definitely seems better then before.
But this phrase
* In such cases, you can use other available methods
* to retrieve the original translation.Feel if we are going to mention that we should mention what those are or least where someone would go to look.
- ๐ฎ๐ณIndia rassoni Bangalore
Rashmisoni โ made their first commit to this issueโs fork.
- ๐ฆ๐บAustralia mstrelan
Is this specific to
hook_entity_presave
or should we update it forhook_entity_update
as well? Also notehook_ENTITY_TYPE_presave
andhook_ENTITY_TYPE_update
also mention$entity->original
.I'm also wondering if it's better to address this in ๐ Define 'original' as property on the entity object Needs work where the property is defined rather than in the hook documentation.