Skip to content

Warning in a custom button #1236

Answered by akleiner2
msakal20 asked this question in Q&A
Discussion options

You must be logged in to vote

Good spot out! Honestly, we can loosen up the prop types / typescript types to accept string that'll help get rid of these errors (while still maintaining typesafety). Happy to accept PRs!

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by akleiner2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants