feat(datepicker): Add readOnly as a supported Form.Input prop (#23)

* Add `readOnly` as a supported `Form.Input` prop.

This will allow for the datepicker to be used
on mobile devices without the device's
virtual keyboard opening.

* Add `basic readOnly` example to the storybook.

This was mainly to test that my change worked,
but is also a good way to demonstrate the
`readOnly` prop in action.

* Update README.md to reflect new `readOnly` prop support.

Author: jalavosus

README.md

@@ -95,6 +95,7 @@ More examples [here](https://react-semantic-ui-datepickers.now.sh).
 - placeholder
 - size
 - transparent
+- readOnly
 
 ### Dayzed Props
 

src/components/datepicker.js

@@ -48,6 +48,7 @@ const semanticInputProps = [
   'required',
   'size',
   'transparent',
+  'readOnly',
 ];
 
 class SemanticDatepicker extends React.Component {
@@ -70,6 +71,7 @@ class SemanticDatepicker extends React.Component {
     type: PropTypes.oneOf(['basic', 'range']),
     pointing: PropTypes.oneOf(['left', 'right', 'top left', 'top right']),
     filterDate: PropTypes.func,
+    readOnly: PropTypes.bool,
   };
 
   static defaultProps = {

stories/index.js

@@ -30,6 +30,11 @@ storiesOf('Examples', module)
       <SemanticDatepicker onDateChange={console.log} />
     </Content>
   ))
+  .add('Basic Readonly', () => (
+    <Content>
+      <SemanticDatepicker onDateChange={console.log} readOnly={true} />
+    </Content>
+  ))
   .add('Basic with allowOnlyNumbers', () => (
     <Content>
       <SemanticDatepicker allowOnlyNumbers onDateChange={console.log} />