ERFormatterBase standardizes code and behavior for loading referenced entities to display (access check, translation handling...)
TaxonomyFormatterBase has its own duplicate-but-different implementation. We should re-base it on EntityReferenceFormatterBase

+ it still has weird/old side behaviors like modifying the îtems in the entity being viewed, which is an antipattern. Thus, filing as a bug.

Comments

yched’s picture

jibran’s picture

yched’s picture

Status: Active » Postponed
Wim Leers’s picture

Wim Leers’s picture

Wim Leers’s picture

Wim Leers’s picture

Title: TaxonomyFormatterBase should extend EntityReferenceFormatterBase » [PP-4] TaxonomyFormatterBase should extend EntityReferenceFormatterBase
Wim Leers’s picture

Title: [PP-4] TaxonomyFormatterBase should extend EntityReferenceFormatterBase » [PP-3] TaxonomyFormatterBase should extend EntityReferenceFormatterBase
Wim Leers’s picture

Title: [PP-3] TaxonomyFormatterBase should extend EntityReferenceFormatterBase » [PP-2] TaxonomyFormatterBase should extend EntityReferenceFormatterBase
Wim Leers’s picture

Title: [PP-2] TaxonomyFormatterBase should extend EntityReferenceFormatterBase » [PP-1] TaxonomyFormatterBase should extend EntityReferenceFormatterBase
Status: Active » Postponed
amateescu’s picture

Actually, it seems like this should be closed as a duplicate when that lands, no? :)

Wim Leers’s picture

I was actually going to ask you exactly that. I didn't realize the other patch included the formatter changes. I guess the formatter changes must happen in that issue, right?

amateescu’s picture

There are no changes needed AFAIS, that issue simply removes TaxonomyFormatterBase in favor of EntityReferenceFormatterBase.

Wim Leers’s picture

Status: Postponed » Closed (duplicate)

Okay, marking this is a duplicate :)