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

[Backend Rewrite] Posts #214

Open
1 task
RobbinBaauw opened this issue Dec 21, 2019 · 2 comments
Open
1 task

[Backend Rewrite] Posts #214

RobbinBaauw opened this issue Dec 21, 2019 · 2 comments

Comments

@RobbinBaauw
Copy link
Owner

@RobbinBaauw
Copy link
Owner Author

RobbinBaauw commented Jan 27, 2020

It would also be nice to have an endpoint where the client just gets the bare minimum paginated information.

Right now, a request is first sent to get all the posts, and then everything about that post is retrieved (except for the content). This can be replaced by a single endpoint which provides the title and some date information of the currently visible posts.

Upon clicking on a post it will send a request to the server to either retrieve the content etc (if not cached), or it will just check if there are any updates. The service worker on the client should be extended to cache everything, so we basically never have to wait and everything will be much snappier.

For this issue this concretely means that the endpoint for retrieving "postHashes" of a topic will be replaced by an endpoint which gets both these "postHashes" and the title and date information. The service worker stuff can be done with the current endpoints and only requires changes on the client.

@NULLx76
Copy link
Collaborator

NULLx76 commented Jan 27, 2020

It would be a substantially bigger change but we could also add a GraphQL(-like) API, so that the client can specify exactly what it wants.

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

No branches or pull requests

2 participants