TData and BaseRecord

[dlarsson]

Hi all. In a number of places, where components/hooks etc are generic with respect to the resource type, TData is used, often with the default type BaseRecord. However, in some places (e.g. useTable), TData is constrained to be a subclass of BaseRecord, rather than defaulting to it, and since BaseRecord is defined as

{
  id?: BaseKey;
  [key: string]: any;
}

this means any string is valid as a key. Do we need this constraint? I would have preferred to have the keys restricted to the keys defined by my resource, but with this constraint, any string will pass the type checker.

[dlarsson]

Never mind, I've written too much C++/Java/Haskell to not realize that <TData extends BaseRecord> doesn't mean that my "UserRecord" needs to explicitly extend BaseRecord for this constraint to be fulfilled.