Conversation
|
Thanks for the pull request, @rpenido! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
782ff8f to
36ce6a2
Compare
navinkarkera
left a comment
There was a problem hiding this comment.
@rpenido The editing experience is much better now!
Left some comments about minor typos and small bugs caught by AI.
I noticed that on clicking fullscreen button the modal goes to left side as seen in the screenshot and the Previous button gets misaligned. Is this expected?
| // Transform the custom_parameters field into a list | ||
| if ("custom_parameters" in submitData.values) { | ||
| const customParameters = submitData.values.custom_parameters; | ||
| submitData.values.custom_parameters = JSON.parse(customParameters); |
There was a problem hiding this comment.
We should probably use try-catch block for JSON.parse of user input.
| // Transform the lti_1p3_redirect_uris field into a list | ||
| if ("lti_1p3_redirect_uris" in submitData.values) { | ||
| const redirectUris = submitData.values.lti_1p3_redirect_uris; | ||
| submitData.values.lti_1p3_redirect_uris = JSON.parse(redirectUris); |
|
|
||
| runtime.notify("save", { state: "start" }); | ||
|
|
||
| $.ajax({ |
There was a problem hiding this comment.
Missing contentType: 'application/json'.
| Arguments: | ||
| course_key (opaque_keys.edx.locator.CourseLocator): Course Key | ||
| """ | ||
| return True |
- Introduce Lti1p3Passport model to centralize LTI 1.3 keys and credentials - Move lti_1p3_internal_private_key, lti_1p3_internal_private_key_id, lti_1p3_internal_public_jwk, lti_1p3_client_id, lti_1p3_tool_public_key, and lti_1p3_tool_keyset_url fields from LtiConfiguration to Lti1p3Passport - Add ForeignKey relationship from LtiConfiguration to Lti1p3Passport - Implement passport-based key generation and retrieval - Add clean() validation to Lti1p3Passport to ensure at least one of lti_1p3_tool_public_key or lti_1p3_tool_keyset_url is set - Update validation in LtiConfiguration.clean() to check for passport presence instead of tool key fields - Refactor get_or_create_local_lti_config() to handle passport creation and sync block/passport key configurations - Update API endpoints to work with passport ID instead of configuration ID - Add admin interface for Lti1p3Passport model - Refactor access_token_endpoint and public_keyset_endpoint to use passport ID - Update API and views to work with the new passport model - Generate migration to remove fields from LtiConfiguration table - Update data migration to copy existing configurations to the new Passport model - Update XBlock to store passport ID instead of config ID - Fix copy-paste issue in resource_link_id generation
* Add signal handlers to delete LTI configurations when xblocks or library blocks are deleted * Ensure LTI configurations are properly cleaned up when associated blocks are removed from the system * Update documentation for LTI 1.3 configuration changes to inform users about potential regeneration of client IDs and URLs when public keys are changed
• Fixed spelling errors (configurtion → configuration, url → URL) • Improved log messages to be more informative • Used more descriptive variable names (id_list → block_locations) • Maintained consistent code style and import organization
- Added 'name' and 'context_key' fields to Lti1p3Passport model - Modified LtiConfiguration to populate these fields when creating passports - Updated admin interface to display new fields - Added migration to populate existing passports with name and context_key - Updated string representation of passport to include name - Made 'location' field in LtiConfiguration unique to prevent race conditions This fixes a race condition that occurred when get_or_create was called with the same location multiple times, which resulted in duplicate rows with identical locations being created simultaneously.
df351e8 to
33750d0
Compare
Adds tests covering possible cases
7d8ddc8 to
4039060
Compare
4039060 to
aade929
Compare
This PR implements a new Edit dialog for the LTI Consumer block
Testing instructions
Private ref: FAL-4322