MDL-82919 introduces a new core_ltix Deep Linking API, which is a significant step toward making the deep linking process more flexible and robust. The mechanisms responsible for initiating content selection and handling return data to are now taking a more generalized approach by accepting a general context ID, rather than being constrained to a course ID.

However, despite these improvements, the implementation still remains tightly coupled to the course context. This limitation arises because the legacy (mod_lti - specific) calls, such as initiating the login and creating a content item request, which continues to rely on a course ID (or course object). While this dependency is currently functional due to mod_lti being the only user of the Deep Linking API, this coupling reduces the scalability and adaptability of the API for broader use cases.

Therefore, the aim of this issues is to move away from this dependency which is critical for future-proofing the API.

Scope:

• Understand the Current Dependencies
  • Analyze how the current Deep Linking API (e.g., core_ltix/contentitem.php and core_ltix/contentitem_return.php) relies on course-specific context by identifying all legacy calls that require a course ID (or course object).
• Integrate the core_ltix Builder API
  • Replace the legacy course-dependent calls in contentitem.php and contentitem_return.php with the generalized methods provided by the core_ltix builder API.
• Refactor core_ltix Deep linking API
  • Refactor the core_ltix Deep Linking API to remove any redundant or course-specific logic that is no longer needed after integrating the builder API.