Open JeffersonBledsoe opened 1 month ago
@sneridagh what do you think of this proposal?
@JeffersonBledsoe let's talk, because what you are saying it's not true. In the PoCs the typings are gotten right. I can show you anytime. It worked right the last time, and if it's not, we have a regression. This is the magic of using TanStack Query...
@JeffersonBledsoe oh, I see, you are not using declaration merging. As said, this is the only way to go in TS to get all right.
@JeffersonBledsoe ok I gave it a second read, sorry but these days are frentic. Let's talk at the meeting.
Is your feature request related to a problem? Please describe.
Currently to get correct typing for a
getContent
query using@plone/client
, we have to do something like the following:Having to do
{ data }: { data: CustomContentType }
is a little verbose and becomes even more so once you destructure additional keys from the query. You can do something likeconst customData = data as CustomContentType
, but it's still extra codeProposed solution
Allow
getContentQuery
to be passed a generic for it's return type. E.g.getContentQuery<CustomContentType>({ path: flattenToAppURL(pathname) })