feat: [FC-0070] rendering library content in unit page

[ihor-romaniuk]

🚨 Dependencies:

• ✅ 🔗 frontend-app-authoring MERGED
• ✅ 🔗 frontend-app-authoring MERGED
• ✅ 🔗 frontend-app-authoring MERGED
• ✅ 🔗 edx-platform MERGED

Description

This feature introduces functionalities to improve XBlock interactions within iframes:

• Add styles that adopt default styles for Library Content which renders chromless template via iframe in MFE Authoring.
• When the isIframeEmbed option is enabled, the XBlock sends a postMessage to the parent window. When sending such a message, the standard link transition is cancelled and the transition is carried out in MFE Authoring.

Unit_Library_Content.mov

Related Pull Requests

• feat: [FC-0070] rendering library content in unit page frontend-app-authoring#1475 - rendering library content in unit page

Testing instructions

• Create a new course.
• Create several units.
• Open the course unit page.
• Add a Library xBlock to the unit.
• Click the “View” button on the Library xBlock.

Note: The change requires rebuilding static assets with tutor dev exec lms opensx-assets build --env=dev

[openedx-webhooks]

Thanks for the pull request, @ihor-romaniuk!

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

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.

---

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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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.

[bradenmacdonald]

Testing instructions

Testing instructions are missing a rebuild of static assets. This PR didn't work for me until I ran tutor dev exec lms openedx-assets build --env=dev

[bradenmacdonald]

I would prefer if we can also send the usageId as a separate parameter in the payload here, instead of making the MFE parse it (const newUnitId = payload.destination.split('/').pop()).

[ihor-romaniuk]

You are right. We can simplify payload data and reduce extra calculation on the MFE side.