refactor: MailtoLink component migrated to TS

[jesusbalderramawgu]

Description

Migration of MailToLink component to TypeScript following this issue

Merge Checklist

• Does your change adhere to the documented style conventions?
• Is there adequate test coverage for your changes?

Post-merge Checklist

• Verify your changes were released to NPM at the expected version.
• If you'd like, share your contribution in #show-and-tell.
• 🎉 🙌 Celebrate! Thanks for your contribution.

[openedx-webhooks]

Thanks for the pull request, @jesusbalderramawgu!

This repository is currently maintained by @openedx/committers-paragon.

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:

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

[netlify]

✅ Deploy Preview for paragon-openedx-v23 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	2311575
🔍 Latest deploy log	https://app.netlify.com/projects/paragon-openedx-v23/deploys/699e1e42f65304000807d15e
😎 Deploy Preview	https://deploy-preview-4140--paragon-openedx-v23.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 94.31%. Comparing base (dfc69e2) to head (2311575).
⚠️ Report is 46 commits behind head on release-23.x.

Additional details and impacted files

@@               Coverage Diff                @@
##           release-23.x    #4140      +/-   ##
================================================
- Coverage         94.39%   94.31%   -0.08%     
================================================
  Files               242      242              
  Lines              4296     4307      +11     
  Branches           1020      988      -32     
================================================
+ Hits               4055     4062       +7     
- Misses              237      241       +4     
  Partials              4        4              

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mphilbrick211]

Hi @openedx/committers-paragon would someone be able to take a look at this for us? Thanks!

[Kelketek]

@jesusbalderramawgu This looks like a change to the API of the component. We can expect this to break downstream uses of it. Is there a particular reason we need to make this change as part of the TypeScript conversion?

[bradenmacdonald]

@Kelketek This change is only in the test code, and in the actual code, content was deprecated in favor of children 7 years ago (!), so I think this is fine :)

paragon/src/MailtoLink/index.tsx

Lines 81 to 86 in 2311575

	export default withDeprecatedProps(MailtoLink, 'MailtoLink', {
	content: {
	deprType: DeprTypes.MOVED,
	newName: 'children',
	},
	});

[bradenmacdonald]

The prop types are not showing up properly on the docs site: https://deploy-preview-4140--paragon-openedx-v23.netlify.app/components/mailtolink/#props-api

The reason is what's mentioned on #3739:

🤔 Note that components using forwardRef require a very specific syntax in order for the props documentation to be detected correctly:

❌ Won't work (props documentation will be missing)	✅ Works (props will be documented)

Please fix that and then I think this should be good to go.