feat: update lti API to pick config via launch data
Note that this uses config_id (the UUID) not config.id (the int) This required a way to get config_id if we only have the block. And it means that we are more likely to go through load_block_as_user because we have not created the config off the block even when calling from the block (since the block has to go through that config ID). A lot of tests had to be updated to have more complete configuration setup because config_id is now load bearing.
Showing
- CHANGELOG.rst 14 additions, 2 deletionsCHANGELOG.rst
- lti_consumer/__init__.py 1 addition, 1 deletionlti_consumer/__init__.py
- lti_consumer/api.py 52 additions, 51 deletionslti_consumer/api.py
- lti_consumer/lti_xblock.py 6 additions, 8 deletionslti_consumer/lti_xblock.py
- lti_consumer/templatetags/get_dl_lti_launch_url.py 0 additions, 1 deletionlti_consumer/templatetags/get_dl_lti_launch_url.py
- lti_consumer/tests/unit/test_api.py 94 additions, 117 deletionslti_consumer/tests/unit/test_api.py
- lti_consumer/tests/unit/test_lti_xblock.py 3 additions, 5 deletionslti_consumer/tests/unit/test_lti_xblock.py
Loading
Please register or sign in to comment