The synchronous {fields, info} state buildData returns -- structurally
just DataState<InferFields<TFields>>, not a distinct shape. This alias
exists so buildData's own signature reads as "the shape buildData
specifically returns," which is more informative at that one call site
than a bare DataState would be; every other consumer should keep using
DataState directly.
The synchronous
{fields, info}statebuildDatareturns -- structurally justDataState<InferFields<TFields>>, not a distinct shape. This alias exists sobuildData's own signature reads as "the shapebuildDataspecifically returns," which is more informative at that one call site than a bareDataStatewould be; every other consumer should keep usingDataStatedirectly.