-
Notifications
You must be signed in to change notification settings - Fork 4
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
Download content pack even when there is content #866
Conversation
@@ -145,29 +149,26 @@ export function decideWelcome(store) { | |||
|
|||
return Promise.all([getDownloadStatus(), getShouldResume()]).then( | |||
([status, { shouldResume, grade, name }]) => { | |||
if (_isDownloadOngoing(status) || shouldResume) { | |||
console.log(['MANUQ', status, shouldResume, grade, name]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you drop or replace this string with something more descriptive?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha, this was a print leftover.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me if you can clean up the debug message. One of these days I'll learn how all the routing works... It would also be nice to store the download state in the backend database someday.
Change the assumption for showing the welcome screens: before, when there was content in the database it was assumed to be already downloaded and the download was skipped. Now rely on the presence of a DOWNLOAD_COMPLETED state persisted. Fix #863
f21dd08
to
a935f95
Compare
The routing is a pain. I have checked in latest Kolibri and the situation didn't improve. So Kolibri has a wrapper around vue-router which plugins use passing a routes object. But also Kolibri has a SET_PAGE_NAME and the current page is used to display a different component in the root view (in our case in the ExplorePlugin). And in the same root has a
Yeah.. that was the idea when implementing content packs management (install more packs, remove packs, etc). |
Change the assumption for showing the welcome screens: before, when there was content in the database it was assumed to be already downloaded and the download was skipped. Now rely on the presence of a DOWNLOAD_COMPLETED state persisted.
Fix #863