Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add types for <ModalDialog> and some related components #3242

Merged
merged 2 commits into from
Oct 17, 2024

Conversation

bradenmacdonald
Copy link
Contributor

@bradenmacdonald bradenmacdonald commented Oct 8, 2024

Description

This adds TypeScript types for:

  • ModalContext
  • ModalDialog
  • ModalDialog.Header
  • ModalLayer
  • Portal

Before this change - no type checking in IDE, no inline docs:
Screenshot

After this change - type checking in IDE:
Screenshot showing missing title property

After this change - inline documentation of props in the IDE:
Screenshot

Deploy Preview

TBD

How to test

  1. Fix the version in package.json by setting it to the latest published version (22.8.2, not 20.x!)
  2. Check out this branch
  3. Install it into any MFE that uses ModalDialog using npm install --save ../paragon
  4. Check any usages of <ModalDialog> in .tsx files or in .jsx files that have // @ts-check at the beginning. You can add // @ts-check to the .jsx files if it's not there already.

Merge Checklist

  • If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
  • Does your change adhere to the documented style conventions?
  • Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
  • Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
  • Were your changes tested in the example app?
  • Is there adequate test coverage for your changes?
  • Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please request an a11y review for the PR in the #wg-paragon Open edX Slack channel.

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
Copy link

Thanks for the pull request, @bradenmacdonald!

What's next?

Please work through the following steps to get your changes 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.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/paragon-working-group. Tag them in a comment and let them know that your changes are ready for review.

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.

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Oct 8, 2024
Copy link

netlify bot commented Oct 8, 2024

Deploy Preview for paragon-openedx ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 620153b
🔍 Latest deploy log https://app.netlify.com/sites/paragon-openedx/deploys/670586d75ede110008400014
😎 Deploy Preview https://deploy-preview-3242--paragon-openedx.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

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

Copy link

codecov bot commented Oct 8, 2024

Codecov Report

Attention: Patch coverage is 95.23810% with 1 line in your changes missing coverage. Please review.

Project coverage is 93.31%. Comparing base (d3fdb89) to head (620153b).
Report is 75 commits behind head on master.

Files with missing lines Patch % Lines
src/Modal/ModalContext.tsx 75.00% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3242      +/-   ##
==========================================
+ Coverage   93.27%   93.31%   +0.03%     
==========================================
  Files         249      249              
  Lines        4401     4441      +40     
  Branches     1038     1049      +11     
==========================================
+ Hits         4105     4144      +39     
- Misses        290      291       +1     
  Partials        6        6              

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

@@ -63,7 +68,7 @@ function ModalLayer({
return null;
}

const handleClose = isBlocking ? null : onClose;
const handleClose = isBlocking ? undefined : onClose;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fixing a minor type error - handleClose was getting passed to <FocusOn> via onEscapeKey but was sometimes null, whereas onEscapeKey expects either a function or undefined, not null.

Type 'null' is not assignable to type '((event: Event) => void) | undefined'.ts(2322)
types.d.ts(15, 5): The expected type comes from property 'onEscapeKey'

@bradenmacdonald bradenmacdonald merged commit ba29749 into openedx:master Oct 17, 2024
11 checks passed
@bradenmacdonald bradenmacdonald deleted the braden/modal-types branch October 17, 2024 16:18
@bradenmacdonald
Copy link
Contributor Author

Thanks @PKulkoRaccoonGang !

@openedx-semantic-release-bot

🎉 This PR is included in version 22.9.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@openedx-semantic-release-bot

🎉 This PR is included in version 23.0.0-alpha.7 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants