-
Notifications
You must be signed in to change notification settings - Fork 72
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 typings for hooks #3125
feat: add typings for hooks #3125
Conversation
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 approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo 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:
🔘 Get a green buildIf 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 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:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
❌ Deploy Preview for paragon-openedx failed.Built without sensitive environment variables
|
f30998a
to
fbb8045
Compare
OK, this is very weird. Without any the other changes, merely renaming |
@@ -12,7 +12,7 @@ window.ResizeObserver = window.ResizeObserver | |||
})); | |||
|
|||
function TestComponent() { | |||
const [containerElementRef, setContainerElementRef] = React.useState(null); | |||
const [containerElementRef, setContainerElementRef] = React.useState<HTMLDivElement | null>(null); | |||
const overflowElementRef = React.useRef(null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit/question: should both refs get the same type with HTMLDivElement
, given both refs are applied to divs
below?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done: a3fea9e
Note that changing it to useRef
instead of useState
for consistency seems to make one of the tests fail, so I've just left one as useState
and one as useRef
for now, but at least they're both HTMLDivElement
refs.
@@ -19,7 +20,7 @@ const resetHandlerMocks = () => { | |||
}; | |||
|
|||
// eslint-disable-next-line react/prop-types |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit/unrelated suggestion: could opt to disable prop-types rule for *.test.*
files so we don't need to have these eslint disable comments throughout test files.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but I'm gonna leave that out of this PR for now.
src/hooks/useArrowKeyNavigation.tsx
Outdated
function handleEnter( | ||
{ event, currentIndex, activeElement }: { event: KeyboardEvent, currentIndex: number, activeElement: HTMLElement }, | ||
) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
curious/suggestion: would it improve readability/understandability of these types if these function args and the return data structure were abstracted into an interface
? E.g., something like the following:
interface HandleEnterOptions {
event: KeyboardEvent;
currentIndex: number;
activeElement: HTMLElement;
}
function handleEnter({ event, currentIndex, activeElement }: HandleEnterOptions) { ... }
Similar question for handleArrowKey
below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure :) a3fea9e
containerElementRef: Element | null, | ||
overflowElementRef: Element | null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit/clarification: should these Element
be HTMLElement
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah - done in a3fea9e
src/hooks/useIsVisible.tsx
Outdated
isVisible: boolean, | ||
sentinelRef: React.MutableRefObject<HTMLDivElement | null>, | ||
] => { | ||
const sentinelRef = useRef<HTMLDivElement | null>(null); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[clarification] Will this sentinelRef
always be applied to a Div
element? Might it be used with non-div
elements, too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point, changed to HTMLElement
a3fea9e
@bradenmacdonald just checking in to see if this is still in progress! |
@mphilbrick211 Thanks for the reminder. I lost momentum on this but now that I have @adamstankiewicz's feedback I would like to pick it up again soon! |
Update: I tried to move this forward, but I'm blocked on some strange webpack bug where it is confusing |
I pulled the branch and got the docs site to build/run locally with a less than ideal workaround. I added I'll do a little more digging to see if I can come up with a better option. |
I tried another thing which seems to work (I haven't clicked around all the docs site pages yet) diff --git a/www/gatsby-config.js b/www/gatsby-config.js
index e3976a0b2c..c0ae5209a2 100644
--- a/www/gatsby-config.js
+++ b/www/gatsby-config.js
@@ -34,6 +34,7 @@ const plugins = [
},
},
'gatsby-plugin-react-helmet',
+ 'gatsby-plugin-typescript',
{
resolve: 'gatsby-plugin-manifest',
options: {
|
9c10177
to
23ee64b
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-22.x #3125 +/- ##
================================================
+ Coverage 93.42% 93.43% +0.01%
================================================
Files 250 251 +1
Lines 4515 4522 +7
Branches 1017 1057 +40
================================================
+ Hits 4218 4225 +7
+ Misses 294 290 -4
- Partials 3 7 +4 ☔ View full report in Codecov by Sentry. |
✅ Deploy Preview for paragon-openedx-v22 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
7b95f95
to
a3fea9e
Compare
@adamstankiewicz Sorry for the long delay in addressing your review, and thanks SO much to @brian-smith-tcril for helping me figure out the very obscure bug that had me stumped. This is ready for another review ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@@ -34,6 +34,7 @@ const plugins = [ | |||
}, | |||
}, | |||
'gatsby-plugin-react-helmet', | |||
'gatsby-plugin-typescript', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note for reviewers: you may have noticed there are no package.json
changes adding this, that is because gatsby-plugin-typescript
is already a dependency of gatsby
(v4 at least - I assume later versions as well) https://www.npmjs.com/package/gatsby/v/4.14.1?activeTab=dependencies
🎉 This PR is included in version 22.13.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
This PR adds typescript types for the various hooks that Paragon provides:
useWindowSize
,useToggle
,useArrowKeyNavigation
,useIndexOfLastVisibleChild
, anduseIsVisible
. There should be no changes other than to the typings.Deploy Preview
https://deploy-preview-3125--paragon-openedx-v22.netlify.app/
Merge Checklist
n/a - doesn't apply to this type of PR.
Post-merge Checklist