Richard Tibbles
Richard Tibbles
Currently, all core shared components are loaded onto the core API object, which leads to a large, bloated object that we load on every single page of Kolibri. In conversation...
## Summary * Updates installation type inference now that Django runserver is no longer used ## References Fixes #7680 ---- ## Testing checklist - [ ] Contributor has fully tested...
While our internal version strings for kolibri user major, minor, patch - some of our plugins, for simplicity, just use major, minor. This breaks when we try to use some...
## Observed behavior On small screens, we may attempt to load many more thumbnail images than might be immediately needed. This can cause slowness and use excessive bandwidth. ## Expected...
Because of the extra technical complexity of allowing learners to sign up on a learner only device, it is currently disabled. To allow the most flexibility for learner sign up,...
## Observed behavior The resume fetches for contentnodes are not ordered by the interaction. ## Expected behavior The most recently interacted content node should be returned first!
## Observed behavior Further, when an image is cloned from a provisioned device, this can cause the same facility to be present on multiple devices unintentionally. ## Expected behavior Automatically...
Currently the webpack variable `__webpack_public_path__` is setup in default frontend and `kolibri_module.js` by importing a special module and executing a function. It would be better if this were automatically inserted...
We currently have two sets of utilities that attempt to completely hard delete a facility and all related metadata - due to the complexity of this task, and the history...