-
Notifications
You must be signed in to change notification settings - Fork 45
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
Custom Component Errors/Warnings #50
Labels
Comments
Thanks for this report! I'll look into reproducing this. I know the If I have time I'll take a stab at a PR, but would love help from others! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to use a custom component, one can trying passing a string or a whole component.
String
Does not seem to be a common pattern for passing a component
Problems
Full Component
Seems to the common method of accepting a component as a prop used in Libraries like
material-ui
like here. That way props can be passed and set within the component (like you are doing with key).Problems
addComponentAsRefTo
is still thrown (might be due to npm-linking causing react version conflicts):The text was updated successfully, but these errors were encountered: