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

Firing unnecessary API endpoint, on homepage. #5

Open
nhwaani opened this issue Feb 7, 2018 · 1 comment
Open

Firing unnecessary API endpoint, on homepage. #5

nhwaani opened this issue Feb 7, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@nhwaani
Copy link
Collaborator

nhwaani commented Feb 7, 2018

As we scroll down to fetch previous posts, say at some point, we open some question to read the info in it, then we go back to homepage, as we reach homepage API is hit, refreshing all the data , thus removing the track i.e on which question the user was before pushing detail question page. Thus he needs to scroll n hit API again to fetch older pages , and this will happen to all previous questions.

@nhwaani nhwaani added the bug label Feb 7, 2018
@nhwaani nhwaani added this to the Important milestone Feb 7, 2018
@nhwaani nhwaani self-assigned this Feb 7, 2018
@nhwaani
Copy link
Collaborator Author

nhwaani commented Feb 7, 2018

Suggestion: As we scroll down to get older questions, then at sometime (unknown) say user clicks the detail page, after coming back from this page, there should be no API call to server, i.e when user clicks back button, there should be API call only if user edited ,added, deleted any resource .
For the rest cases no API must be fired.

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

No branches or pull requests

1 participant