Field-level resolution in core data

[adamziel]

Core data should consider entities resolved during getEntityRecords() as also resolved for the purposes of the individual getEntityRecord() calls.

The problematic part is _fields part of the query. Calling getEntityRecords() without specifying _fields requests a "full" list of entities. If one passes _fields as a part of the query, the API will return only a subset of fields.

After merging #26575, getEntityRecord() will only be resolved by getEntityRecords() if _fields are missing from the query. This a good start, but it would still be possible to resolve specific entities as long as the same or a smaller subset of fields is requested. Otherwise an API round-trip would be required to fetch the missing fields.

One way to implement that would be having a more granular resolution mechanism. Something like "resolution per entity field" instead of "resolution per selector".

Related discussions:

• https://github.com/WordPress/gutenberg/pull/26575/files#r515941794
• Concurrency control in core-data #26325

[jordesign]

Hey @adamziel - I'm just looping back through some older issues. Wanted to see if this one has been resolved in the interim?

[Mamaduka]

Hey, @jordesign. This logic hasn't been implemented yet.