-
Notifications
You must be signed in to change notification settings - Fork 44
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
upkeep: Add TS support for Optional
component
#298
Merged
Merged
Changes from 2 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
a3485d0
move Optional component to TS
Sidsector9 8b862f4
eslint fix
Sidsector9 1cab61d
remove proptypes
Sidsector9 229c1f3
add doc
Sidsector9 3630823
Update components/optional/index.ts
Sidsector9 60b34bf
Merge branch 'upkeep/component-optional' of github.com:10up/block-com…
Sidsector9 a7391dc
Merge branch 'develop' into upkeep/component-optional
Sidsector9 dc65fef
remove default props
Sidsector9 355e598
Merge branch 'upkeep/component-optional' of github.com:10up/block-com…
Sidsector9 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,15 @@ | ||
import PropTypes from 'prop-types'; | ||
import { useBlockEditContext } from '@wordpress/block-editor'; | ||
|
||
export const Optional = ({ value, children }) => { | ||
interface OptionalProps { | ||
value?: string | number | boolean; | ||
children: React.ReactNode; | ||
} | ||
|
||
export const Optional: React.FC<OptionalProps> = ({ | ||
value, | ||
Sidsector9 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
children, | ||
}): boolean | React.ReactNode => { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure we need / want to explicitly type the return type of every function. If something can be inferred I would rather just leave it up to the compiler |
||
const { isSelected } = useBlockEditContext(); | ||
return (isSelected || !!value) && children; | ||
}; | ||
|
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.
I actually think that as part of converting something to TypeScript it makes sense to get rid of all the PropTypes stuff.