You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, a major source of SSR and general loading bugs is from forgetting to specify knownColumns and initialData in the query definition. This is in no small part due to the weird requirement for the user to specify it, instead of it being handled internally - the users aren't directly writing to the SSR cache, but for some reason, they have to manually read from it
The fix to this is having some mechanism for setting or otherwise providing Query with $page.data.data, so instead of this:
const{ results, update }=buildReactiveInputQuery({ value, data, label, order, where },`ButtonGroup-${name}`,$page?.data?.data[`ButtonGroup-${name}_data`]);
it would be this:
const{ results, update }=buildReactiveInputQuery({ value, data, label, order, where },`ButtonGroup-${name}`);
not even sure buildReactiveInputQuery works right now considering it doesn't read knownColumns
The text was updated successfully, but these errors were encountered:
Right now, a major source of SSR and general loading bugs is from forgetting to specify
knownColumns
andinitialData
in the query definition. This is in no small part due to the weird requirement for the user to specify it, instead of it being handled internally - the users aren't directly writing to the SSR cache, but for some reason, they have to manually read from itThe fix to this is having some mechanism for setting or otherwise providing
Query
with$page.data.data
, so instead of this:it would be this:
not even sure
buildReactiveInputQuery
works right now considering it doesn't readknownColumns
The text was updated successfully, but these errors were encountered: