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

Filter by hashtag? #4

Open
alexmacarthur opened this issue Dec 17, 2018 · 6 comments
Open

Filter by hashtag? #4

alexmacarthur opened this issue Dec 17, 2018 · 6 comments

Comments

@alexmacarthur
Copy link
Owner

No description provided.

@g3ortega
Copy link
Contributor

I've been looking for a way to get docs by folder and it seems they don't support it (at least in the current version of the API). Is there a way to filter by hashtag? If so, I can help with that.

One of the problems I have right now is the time it takes to load all the documents, hopefully they improve the API soon.

@jamessimone
Copy link
Contributor

@g3ortega on the subject of loading time: Gatsby offers caching for created nodes but we would have to change the id passed to the createNodeId function in the DocumentManager to use the metadata id from Paper in order to cache the rest of the document (but this would substantially speed up the API because the metadata call is quite fast). I have tested this locally, caching the last_updated_date and the metadata id in order to preserve the existing Gatsby node unless the current last_updated_date differs from the one in Gatsby’s cache.

If @alexmcarthur is open to it, I’m happy to put the PR with that code up here.

@alexmacarthur
Copy link
Owner Author

@jamessimone Please do! Curious about the node caching you're talking about. I'm not to that level of familiarity with Gatsby's API to make that happen.

@jamessimone
Copy link
Contributor

@alexmacarthur just opened #8 for that!

@g3ortega
Copy link
Contributor

@jamessimone, just curious, how is handled the expiration in that case? can we set the expiration time or something like that?

@jamessimone
Copy link
Contributor

@g3ortega I am not sure of Gatsby’s internal expiration handling of the .cache folder; if any, but my guess is that all caching between builds that isn’t explicitly set using this paradigm (which in the case of Dropbox paper would be based off of the last modified date for each individual doc) just gets rebuilt into that folder

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