Skip to content

refactor: remove built-in LTI XBlock implementation (slash-n-burn #37819) - #38747

Open
irfanuddinahmad wants to merge 7 commits into
masterfrom
irfanuddinahmad/slash-and-burn-lti-block
Open

irfanuddinahmad wants to merge 7 commits into
masterfrom
irfanuddinahmad/slash-and-burn-lti-block

Conversation

@irfanuddinahmad

@irfanuddinahmad irfanuddinahmad commented Jun 11, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Removes the built-in LTI XBlock. xblock_lti.LTIBlock has been the default since USE_EXTRACTED_LTI_BLOCK = True, so the built-in code no longer runs.

Part of the Slash-n-Burn Built-In XBlocks epic. Closes openedx/public-engineering#537

Merge status: ✅ ready for review.
Known gaps: none. lms/djangoapps/lti_provider/ is out of scope.
Translations hold: merge only after openedx/xblocks-core#329 and openedx/openedx-translations#85196 are live and the xblock_* catalogs are confirmed. Until then the extracted block is translated only through the built-in xmodule msgids that this PR deletes. Its lti_form.html string also needs i18n_service (review on #329).

Changes

Deleted: xmodule/lti_block.py (built-in class + shim), xmodule/lti_2_util.py (now xblock_lti.lti_2_util), xmodule/js/src/lti/lti.js, xmodule/js/fixtures/lti.html, LTIBlockDisplay.css, lms/templates/lti.html and lti_form.html, the LTIBlockDisplay/LTIBlockEditor webpack entries and the imports-loader rule for lti/lti.js, the built-in lti entrypoint, and the USE_EXTRACTED_LTI_BLOCK toggle.

Modified: lms/envs/common.py drops the two built-in LTI handlers from XBLOCK_NOAUTH_HANDLER_ALLOWLIST. They can no longer be imported, which would fail test_default_allowlist_entries_import; the xblock_lti entries stay on the list.

Tests:

Removed from the platform Counterpart in xblocks-core
xmodule/tests/test_lti_unit.py, test_lti20_unit.py (43 tests) src/xblock_lti/tests/: same names, near-identical bodies (compared one by one)

Kept in the platform:

  • lms/djangoapps/courseware/tests/test_lti_integration.py: toggle branches collapsed to the extracted path, BuiltIn twin classes and importlib.reload(lti_block) dropped.
  • lms/djangoapps/courseware/tests/test_block_render.py: imports from xblock_lti.

Epic Step 1: Post-extraction commit review

Toggle flipped 2026-02-02 (bcddf9cd53). All 5 later commits to lti_block.py/lti_2_util.py are cosmetic (deprecation markers #38174, ruff suppression, style, import sorting, lint-amnesty). The one pre-toggle fix, a Library v2 preview fix (cc56e41d0c), is already in xblocks-core ("fix: fix LTI XBlock preview in Content Library"). Nothing to port.

Test plan

Tested on a local Tutor nightly (master 6f85d63c7f + xblocks-core 2.0.0) through the REST APIs and a headless browser, because PR sandboxes aren't deploying (open-craft/pr-sandbox-automation#28). A box is ticked only if that flow actually ran.

  • LMS student view
  • CMS course unit
  • CMS V2 Library
  • Signed LTI launch from the library-reused copy in the LMS; no XBLOCK_NOAUTH_HANDLER_ALLOWLIST errors in the logs
  • CI: pytest lms/djangoapps/courseware/tests/test_lti_integration.py (5 passed locally) and test_block_render.py (166 passed), npm run build; the lti entrypoint resolves to xblock_lti:LTIBlock
V2 Library checklist: 11/12 pass (L10 export diff not done)

Content Libraries V2: smoke tests (historically the most fragile area for extracted blocks: openedx/xblocks-core#123, openedx/xblocks-core#132, openedx/xblocks-core#243, openedx/xblocks-core#274)

  • L1. Create the block in a V2 library; the preview renders with no 500 or console errors
  • L2. Edit → save → reload the page → reopen the editor: every field kept its value
  • L3. Publish the component; its status changes to Published
  • L4. Copy to clipboard from the library, then paste into the library and into a course unit
  • L5. In a library unit: add the block as new content, then add it as existing library content (watch for "There was an error linking the content to this container", [Test failure] TC-00338: Libraries: Unable to add existing component to a unit wg-build-test-release#556)
  • L6. Reuse in a course: add it through "Library content" in a unit, and reuse a library unit containing it from the course outline. Both render in Studio and in the LMS student view
  • L7. Sync: edit and publish in the library, then accept the update in the course and also ignore one
  • L8. Override the title on the reused copy in the course
  • L9. Library search: filtering by content type finds the block
  • L10. OLX: import as a pointer tag and inline, export as a pointer tag, and diff the export against master (which still has the built-in block) — not ticked: inline and pointer-tag import and pointer-tag export pass; the export diff against the built-in block wasn't done

LTI-specific:

Library checklist compiled from the Aximprovements manual test doc (Extracted Block Tests tab) and the Ulmo test sheet's library cases. Generated using Claude Code.

Screenshots

5 screenshots (LMS, Studio unit, V2 Library)

Local Tutor nightly, 2026-11-12

Captured automatically during the local smoke tests (the sandbox isn't reachable yet, see open-craft/pr-sandbox-automation#28). All images: irfanuddinahmad/edx-platform@snb-smoke-screenshots/38747.

LMS student view (imported block) Studio course unit (authoring MFE)
lms_inline studio_unit
V2 library home V2 library component preview
library_home lib_preview
LMS: copy reused from the library (after sync + title override)
lms_reused

🤖 Generated with Claude Code

Settings

# Workaround for open-craft/pr-sandbox-automation#28: the openedx-permissions image name gets mangled.
DOCKER_IMAGE_PERMISSIONS: docker.io/overhangio/openedx-permissions:23.0.0-main

@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels Jun 11, 2026
@openedx-webhooks

openedx-webhooks commented Jun 11, 2026 •

Copy link
Copy Markdown

Thanks for the pull request, @irfanuddinahmad!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform-oncall.

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 approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To 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:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where 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:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Jun 11, 2026
@irfanuddinahmad
irfanuddinahmad force-pushed the irfanuddinahmad/slash-and-burn-lti-block branch from 7eb55b9 to 6a680a4 Compare June 11, 2026 12:52
@mphilbrick211 mphilbrick211 moved this from Needs Triage to Waiting on Author in Contributions Jun 11, 2026
@irfanuddinahmad
irfanuddinahmad force-pushed the irfanuddinahmad/slash-and-burn-lti-block branch 2 times, most recently from 3885169 to 0da9a28 Compare June 12, 2026 16:55
@irfanuddinahmad
irfanuddinahmad force-pushed the irfanuddinahmad/slash-and-burn-lti-block branch 3 times, most recently from 0da9a28 to 9ebb7e9 Compare June 22, 2026 11:22
@irfanuddinahmad irfanuddinahmad changed the title feat: remove built-in LTI XBlock implementation (slash-n-burn #37819) refactor: remove built-in LTI XBlock implementation (slash-n-burn #37819) Jun 22, 2026
@mphilbrick211 mphilbrick211 moved this from Waiting on Author to Ready for Review in Contributions Jul 13, 2026
@irfanuddinahmad
irfanuddinahmad force-pushed the irfanuddinahmad/slash-and-burn-lti-block branch from 9ebb7e9 to f690abf Compare November 4, 2026 11:11
@irfanuddinahmad irfanuddinahmad added the create-sandbox open-craft-grove should create a sandbox environment from this PR label Nov 5, 2026
Irfan Ahmad and others added 5 commits November 10, 2026 13:14
)

Removes xmodule/lti_block.py, xmodule/lti_2_util.py, all LTI
JS/CSS/template assets, webpack entries, the USE_EXTRACTED_LTI_BLOCK
toggle, and the conflicting `lti` entrypoint in pyproject.toml now
that the extracted version in xblocks-contrib is the only implementation.
Collapses toggle-conditional test classes into single test classes
targeting the extracted-block behavior.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
The built-in LTI block modules no longer exist, so these allowlist
entries cannot be imported and fail test_default_allowlist_entries_import.
The xblocks_contrib.lti equivalents remain on the allowlist.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
xblocks-core 2.0.0 (#38473) removed the xblocks_contrib package. Point the
platform entrypoint, imports and mock.patch targets at the new per-block
packages (e.g. xblocks_contrib.video.video -> xblock_video.block).

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@irfanuddinahmad
irfanuddinahmad force-pushed the irfanuddinahmad/slash-and-burn-lti-block branch from f690abf to db8b616 Compare November 10, 2026 10:25

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). create-sandbox open-craft-grove should create a sandbox environment from this PR open-source-contribution PR author is not from Axim or 2U

Projects

Status: Ready for Review

Development

Successfully merging this pull request may close these issues.

[Refactor] Slash-n-Burn LTI BuiltIn XBlock

2 participants