-
-
Notifications
You must be signed in to change notification settings - Fork 620
Fix/support multi relation property #635
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
Fix/support multi relation property #635
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
hmmmm the @rimonhanna does your use case work with the |
@transitive-bullshit done |
best way to test it, is to enable sub item in this collection and create a few sub items to one of the database items https://react-notion-i5tvrh2a1-saasify.vercel.app/2fea615a97a7401c81be486e4eec2e94 |
@transitive-bullshit any chance this can be merged and released soon? Thanks! |
64857eb
to
0566267
Compare
@transitive-bullshit rebased and conflicts fixed |
@rimonhanna this looks amazing; thank you 🙏 will include in the next release btw, do you have a quick notion page id I can use to add this to the test suite? |
awesome; thanks again, rimon 🙏 |
ahhh actually, what's the notion id of that page? i can't seem to find it on that site |
Description
A database with sub-items enabled
Add multiple sub-items to a single "parent" page
Open parent page:
Previously: It showed only the first child/sub-item as the returned recordMap only included the full information of the first, and only the Ids of the others
Now: It attempts to fetch all children/sub-items blocks and shows them as expected