-
Notifications
You must be signed in to change notification settings - Fork 748
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
Move core notifications handling into NotificationsRoot component #12626
Comments
@rtibbles can you please assign me this issue. |
Yes, assigned! Feel free to ask any follow up questions here! |
What two actions are to be moved as methods in NotificationRoot component. I could only find one action from the given link. |
Hi @iamshobhraj. From function names I would assume the other one could perhaps be |
@iamshobhraj Perhaps you've already done that, so just a general recommendation - always best to preview that logic before/after on the dev server. Then you will also get a mental picture of how the user experience looks like as well as what's going on under the hood, and can use it for verification that it still works as expected after the refactor. Thanks :)! |
- Moved buildkite docker file and changed Makefile accrodingly - New dockerfiles in deploy/ and associated Makefile targets - docs for running Dockerfiles - Do not provision if KOLIBRI_PROVISIONDEVICE_FACILITY is not set - import channels from KOLIBRI_CHANNELS_TO_IMPORT
Closed by #12644 |
Currently all the admin notifications are handled through the core vuex state, but these are only accessed and used in the NotificationsRoot component and its child component UpdateNotifications.
notifications
state should instead be set as a data property on the NotificationsRoot component.getNotifications
should now be called in thecreated
hook of the NotificationsRoot component, and references to the action in kolibri_app.js and its associated spec file should be removednotifications
state key should be deleted along with any associated Vuex mutationsThe text was updated successfully, but these errors were encountered: