-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Convert FocalPointPicker tests to TypeScript #61373
Merged
tyxla
merged 6 commits into
WordPress:trunk
from
jpstevens:update/type-focal-point-picker-tests
May 10, 2024
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
dfdc258
chore: migrate focal-point-picker media tests to typescript
jpstevens 42ad69f
chore: migrate focal-point-picker index tests to typescript
jpstevens 5eb0ba8
fix: remove duplicate internal dependencies comment
jpstevens bd57b12
chore: use `unknown[]` instead of `any[]` for test types
jpstevens c2315a8
chore: extract data-testid to common prop object
jpstevens 1f0812d
Merge branch 'WordPress:trunk' into update/type-focal-point-picker-tests
jpstevens File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Literally every test will have the
data-testid="media"
prop, should we add this toprops
and remove that prop from the tests?We might need to add the
data-testid
prop toFocalPointPickerMediaProps
since that prop doesn't exist there.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 question - I've updated the default prop object to include
'data-testid': 'media'
The change is only required for testing, so I opted not to change the underlying
FocalPointPickerMediaProps
type definition.The current implementation of
Media
uses pass-through props, which allow any prop to be passed to the child component, includingdata-testid
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.
Interestingly, I couldn't find any tests in the codebase where the
data-testid
prop is not repeated on each component:data-testid="elevation"
data-testid="grid"
data-testid="inner-content"
There is one example that extracts the
data-testid
value to a const, but it doesn't prevent the prop repetition on the components:data-testid={ testId }
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.
Thanks for taking such a thorough look! This was a very minor detail and TBH I'm good with you've come up with 👍