-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load views on user load and read in cache #3552
Conversation
08e6d42
to
8630aea
Compare
8630aea
to
668f3e2
Compare
|
||
export const useCachedRootQuery = ({ | ||
objectMetadataItem, | ||
isArrayOfRecords, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not a big fan if isArrayOfRecords, we should stick to the query api: { query: findMany | findOne }. We would likely also pass query variables at some point
isArrayOfRecords: true, | ||
}); | ||
|
||
const { records } = useFindManyRecords({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, the API is not that bad!
} | ||
} | ||
} | ||
views { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
later we should generate this from our mapMetadataToQuery hooks but this would require to have the system standard object available in the FE no matter if we have fetched /metadata already or not. We could also leverage fragment for this part
@thomtrp We are missing the piece on the backend. I've added it |
e4e3f45
to
12ce196
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
This PR: