Size Change: -2 B (0%)

Total Size: 1.5 MB

_{compressed-size-action}

I understand as follows.

• The value of the title property of data retrieved by useEntityRecord(s) or getEntityRecord(s) is always an object with raw and rendered sub-properties
• The value of the title property of data retrieved by getEditedEntityRecord is always a string.

In other words, of the areas refactored in #52807, the direct use of the value of the title property should be limited to those that internally depend on getEditedEntityRecord.

I have looked again at why this difference occurs, and this series of comments seems to be right on target.

Edited records use title: string instead of title: { raw: string, rendered: string; } so that's another special case to handle

Are you talking about the fact that we might store a string in the app but the API response has a different version of the data? If that's the case we may find that we have a different type for the API response and the internal data. That's a good thing though! By the way we can handle these cases through type utilities if the case is general enough and warranted.

Ah, I meant a quirk of how core-data treats certain properties. For example, posts retrieved using getEntityRecord have a title as an object with raw and rendered properties with raw block markup, and its rendered version respectively. If you start editing the data, though, and use getEditedEntityRecord, the title becomes a string containing the edits. These special properties are listed in rawAttributes in entities.js