-
Notifications
You must be signed in to change notification settings - Fork 727
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
Moved login/logout logic into the useUser composable and updated references #12915
base: develop
Are you sure you want to change the base?
Conversation
Put commit ref in external file. Update all static files for new build.
…content_id. Use node_id when available. Query for most recent session log to give parallel results for summary logs.
Take advantage of reduced build time to add to PR build.
…uthmessage w/ urls
…g even if an error occurs mid-navigation (for example, like in QuizSummary's beforeRouteEnter)
…lity_continue Conditionalize hideContinue on whether we are displaying an error or not
…angelog-0.17.4 Update changelog for 0.17.4
# Conflicts: # kolibri/__init__.py
…osition API useUser
Build Artifacts
|
…dabot/npm_and_yarn/katex-0.16.18 Bump katex from 0.16.17 to 0.16.18
Auto update h5p
…osition API useUser
When I did a rebase locally on develop here, it threw up some weird conflicts, but resolving them during the rebase did reduce it down to only about 10 commits, so I think this can be cleaned up! Let me know if it would be helpful for me to force push updates for this. |
Thank you for your help! If you think force pushing the updates would clean up the commit history and make it easier to manage, I would appreciate it. Please go ahead and do so if it's not too much trouble. |
Summary
Login/logout and session logic is moved into
useUser
composable fromaction.js
. Refactored vuex state into module level state. References toCORE_SET_SESSION
is updated to use the setSession method from useUser composable.References
fixes #12204
Reviewer guidance
after updating references to
CORE_SET_SESSION
inheartbeat.spec.js
file, some tests still failed. I am unable to figure out why these tests are failing. I updated the mock file and implementated it as written in documentation.