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

Update DB on signup #73

Closed
dev-ritik opened this issue Nov 8, 2019 · 6 comments · Fixed by #85
Closed

Update DB on signup #73

dev-ritik opened this issue Nov 8, 2019 · 6 comments · Fixed by #85
Assignees
Labels
enhancement New feature or request

Comments

@dev-ritik
Copy link
Member

No description provided.

@dev-ritik dev-ritik added the enhancement New feature or request label Nov 8, 2019
@Arnesh07
Copy link
Member

Arnesh07 commented Nov 8, 2019

Explanation? This has already been tackled in the previous pull request. @dev-ritik

@dev-ritik
Copy link
Member Author

#44 would take considerable time before its merged. Meanwhile, we can solve this issue. Also, at the time of signup, we would only be updating the profile of that particular user only.

@Arnesh07
Copy link
Member

Arnesh07 commented Nov 9, 2019

For this, I would have to copy the whole function RefreshSubmissions() from the previous pull request. One thing I can do is that comment the line in the scheduler that is resulting in the daily API calls to refresh data. @dev-ritik

@dev-ritik
Copy link
Member Author

Copy and making a new PR would be better

@Arnesh07
Copy link
Member

Do we want to refresh the submissions of all the users in the database after any user signs up? Or just fetch his submissions? @dev-ritik

@dev-ritik
Copy link
Member Author

Do we want to refresh the submissions of all the users in the database after any user signs up? Or just fetch his submissions? @dev-ritik

Fetch his own submissions

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

Successfully merging a pull request may close this issue.

2 participants