-
Notifications
You must be signed in to change notification settings - Fork 35
Queries (Reading Data) #132
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
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
discord thread here: https://discord.com/channels/830183651022471199/1378684414166568991 , which i still need to reply to with additional context on my last message regarding shadcn. Regarding the right side mini-nav, i think the reason i don't find myself using it is that its a layout for docs that i'm used to. Not saying that its all that bad, but with how much text is in that photo it requires more time to scan through it all. The analogy here would be similar to creating good postgres indexes in your upstream database lol if you setup it up correctly, it makes the lookups faster. If im working on building a query, i've found myself first focusing on including data (relationships) and then excluding data (filters). So if im in the middle of trying to remember the API for the filtering functions, i'd expect/want to do the following:
|
Overview
NOT READY TO MERGE
This PR attempts to begin to break down the numerous important concepts related to querying data using zero. Majority of content in this PR has already been written before, but has been reorganized/grouped for easier accessibility - particularly for users (like myself) that find themselves frequently re-referencing the docs.
Queries (Reading Data)
@aboodman if you approve of this page structure, i'm happy to invest more time and ensure all the actual content of each page is correct - given that they were generated.