Skip to content
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

fix(Input): spread input props on the input child #916

Merged
merged 2 commits into from
Nov 22, 2016

Conversation

levithomason
Copy link
Member

@levithomason levithomason commented Nov 22, 2016

Fixes #909

This PR spreads props on the input child when using children in advanced input variations. It also updates the docs, hoisting all <input /> props to the <Input /> parent.

I've spread the props so that the input child props win, for backward compatibility. Though, the suggested use here is to use the input child as a placeholder, without props. I've updated the docs to reflect this as well.

@codecov-io
Copy link

Current coverage is 100% (diff: 100%)

Merging #916 into master will not change coverage

@@           master   #916   diff @@
====================================
  Files         137    137          
  Lines        2259   2262     +3   
  Methods         0      0          
  Messages        0      0          
  Branches        0      0          
====================================
+ Hits         2259   2262     +3   
  Misses          0      0          
  Partials        0      0          

Powered by Codecov. Last update 37f4468...b99945b

@levithomason levithomason deleted the fix/child-input-props branch November 22, 2016 19:46
@levithomason
Copy link
Member Author

Released in semantic-ui-react@0.61.3.

Arthelon pushed a commit to Arthelon/Semantic-UI-React that referenced this pull request Nov 23, 2016
* docs(Input): update children usage

* fix(Input): spread input props on the input child
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants