In the destination tab, each block mapping (e.g. "Suggested Itinerary", "Features", "Accommodation") shows the label and its property aliases, but not the element type alias of the block itself.
This makes it hard to tell which backoffice element type a mapping is actually wired to, especially when two similarly-named element types exist (for example during a rename migration). Today we had the label say "Suggested Itinerary" while the underlying mapping pointed at a deprecated misspelt element type alias. The UI gave no visible indication of the mismatch, and content extraction silently failed because the target block wasn't on the page.
Request: Display the contentTypeAlias (and ideally the contentTypeKey) on each block mapping card in the destination view, so editors can verify which element type a mapping targets without opening the underlying JSON.
In the destination tab, each block mapping (e.g. "Suggested Itinerary", "Features", "Accommodation") shows the label and its property aliases, but not the element type alias of the block itself.
This makes it hard to tell which backoffice element type a mapping is actually wired to, especially when two similarly-named element types exist (for example during a rename migration). Today we had the label say "Suggested Itinerary" while the underlying mapping pointed at a deprecated misspelt element type alias. The UI gave no visible indication of the mismatch, and content extraction silently failed because the target block wasn't on the page.
Request: Display the
contentTypeAlias(and ideally thecontentTypeKey) on each block mapping card in the destination view, so editors can verify which element type a mapping targets without opening the underlying JSON.