fix: latex preview not working

[andrii-hantkovskyi]

TL;DR - [ This PR fixes the issue with LaTeX preview ]

What changed?

• [ More in-depth breakdown of changes ]
  Added |add:criterion.name to the preview_name attribute in the {% include %} tag.
• [ Peripheral things that got changed ]
  The order of attributes was slightly adjusted, but no functional impact.
• [ etc... ]

Developer Checklist

• Reviewed the release process
• Translations and JS/SASS compiled not needed
• Bumped version number in openassessment/__init__.py and package.json

Testing Instructions

[ How should a reviewer test this PR? ]

1. Install the plugin from this branch
2. Add an ORA problem for any unit using this instruction
3. Make sure you enabled LaTeX response - specify response, paragraph 5
4. Go to LMS, then the unit where you added the problem
5. Write something in the response field using LaTeX syntax
6. Press Preview in LaTeX
7. You should see formatted text and no Uncaught TypeError: Cannot read properties of undefined (reading 'replace') error in the dev tools console

Reviewer Checklist

Collectively, these should be completed by reviewers of this PR:

• I've done a visual code review
• I've tested the new functionality

FYI: @openedx/content-aurora

[openedx-webhooks]

Thanks for the pull request, @andrii-hantkovskyi!

This repository is currently maintained by @openedx/2u-aurora.

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

🔘 Submit a signed contributor agreement (CLA)

⚠️ We ask all contributors to the Open edX project to submit a signed contributor agreement or indicate their institutional affiliation.
Please see the CONTRIBUTING file for more information.

If you've signed an agreement in the past, you may need to re-sign.
See The New Home of the Open edX Codebase for details.

Once you've signed the CLA, please allow 1 business day for it to be processed.
After this time, you can re-run the CLA check by adding a comment below that you have signed it.
If the CLA check continues to fail, you can tag the @openedx/cla-problems team in a comment for further assistance.

🔘 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.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.

---

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.

[e0d]

@andrii-hantkovskyi we need to have a CLA in place for your contribution. Are you working for a company that has an entity CLA in place?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.29%. Comparing base (f75139d) to head (a4e6995).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2277   +/-   ##
=======================================
  Coverage   95.29%   95.29%           
=======================================
  Files         195      195           
  Lines       21624    21624           
  Branches     1502     1502           
=======================================
  Hits        20606    20606           
  Misses        771      771           
  Partials      247      247           

Flag	Coverage Δ
unittests	95.29% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[andrii-hantkovskyi]

@e0d I'm working for RaccoonGang, waiting for my team to approve.