Skip to content
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

Add optional blockMap content in table endpoint #18

Open
timolins opened this issue Jul 18, 2020 · 3 comments
Open

Add optional blockMap content in table endpoint #18

timolins opened this issue Jul 18, 2020 · 3 comments

Comments

@timolins
Copy link
Member

timolins commented Jul 18, 2020

I think it would be cool to automatically include the blockMap of each item inside a table (optionally).
Currently I have to manually do a request for each entry to receive it. Doing it on the server with caching sounds like a good idea.

@stubclan
Copy link

I second this. I spent almost all day trying to understand your code and try to manually add it (Not a Typescript developer per say) and was wondering if this would ever be added.

I just want to have excerpts of the content on the List page which would be nice to have if we're to setup a blog.

However, I think this should be a feature request rather than an issue.

@transitive-bullshit
Copy link
Contributor

transitive-bullshit commented Aug 23, 2020

@stubclan check out notion-client. It exposes the core API and returns all the data you'd expect. All collection views have been thoroughly tested.

The goal is to convert this project to use notion-client under the hood soon as well.

@stubclan
Copy link

ooo so exciting. Thanks @transitive-bullshit . I like how you guys still say unofficial haha. Notion did say they'll provide API as well someday in future.

Also do you know if I can use my own api-worker for this notion-client ? I kinda spent time on setting up so just curious

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants