add theme validation logic to front-end and provide defaults for tests #151
Labels
category: library
Shared code library
category: supporting code
Implementation of the system
P1 - important
Priority: High impact on UX
type: task
Something that needs to be done
Observed behavior
Having validation only on the backend means that the theme "API" isn't well defined.
Expected behavior
It would be better for the front-end to clearly define it, and possibly to provide internal defaults so that unit testing is easier
see thread: learningequality/kolibri#5688 (review)
User-facing consequences
themes and tests that need themes are confusing for devs to work with
Context
0.12.4
The text was updated successfully, but these errors were encountered: