From e90162191d3a3bb1913b01b32dd27f03f37e76f7 Mon Sep 17 00:00:00 2001 From: Website Deployment Script Date: Fri, 24 May 2019 22:04:55 +0000 Subject: [PATCH] Deploy website Deploy website version based on 709f7ba8007698b0baac14ecd486a4c7a3963a3c --- docs/next/datepickerios.html | 11 ++--------- docs/next/datepickerios/index.html | 11 ++--------- docs/next/state.html | 4 ++-- docs/next/state/index.html | 4 ++-- 4 files changed, 8 insertions(+), 22 deletions(-) diff --git a/docs/next/datepickerios.html b/docs/next/datepickerios.html index d2c081c296e..a06d2b74b89 100644 --- a/docs/next/datepickerios.html +++ b/docs/next/datepickerios.html @@ -133,9 +133,7 @@

onChange

Date change handler.

-

This is called when the user changes the date or time in the UI. -The first and only argument is an Event. For getting the date the picker -was changed to, use onDateChange instead.

+

This is called when the user changes the date or time in the UI. The first and only argument is an Event. For getting the date the picker was changed to, use onDateChange instead.

@@ -233,12 +231,7 @@ was changed to, use onDateChange instead.

TypeRequired

initialDate

-

Provides an initial value that will change when the user starts selecting -a date. It is useful for simple use-cases where you do not want to deal -with listening to events and updating the date prop to keep the -controlled state in sync. The controlled state has known bugs which -causes it to go out of sync with native. The initialDate prop is intended -to allow you to have native be source of truth.

+

Provides an initial value that will change when the user starts selecting a date. It is useful for simple use-cases where you do not want to deal with listening to events and updating the date prop to keep the controlled state in sync. The controlled state has known bugs which causes it to go out of sync with native. The initialDate prop is intended to allow you to have native be source of truth.

diff --git a/docs/next/datepickerios/index.html b/docs/next/datepickerios/index.html index d2c081c296e..a06d2b74b89 100644 --- a/docs/next/datepickerios/index.html +++ b/docs/next/datepickerios/index.html @@ -133,9 +133,7 @@

onChange

Date change handler.

-

This is called when the user changes the date or time in the UI. -The first and only argument is an Event. For getting the date the picker -was changed to, use onDateChange instead.

+

This is called when the user changes the date or time in the UI. The first and only argument is an Event. For getting the date the picker was changed to, use onDateChange instead.

TypeRequired
@@ -233,12 +231,7 @@ was changed to, use onDateChange instead.

TypeRequired

initialDate

-

Provides an initial value that will change when the user starts selecting -a date. It is useful for simple use-cases where you do not want to deal -with listening to events and updating the date prop to keep the -controlled state in sync. The controlled state has known bugs which -causes it to go out of sync with native. The initialDate prop is intended -to allow you to have native be source of truth.

+

Provides an initial value that will change when the user starts selecting a date. It is useful for simple use-cases where you do not want to deal with listening to events and updating the date prop to keep the controlled state in sync. The controlled state has known bugs which causes it to go out of sync with native. The initialDate prop is intended to allow you to have native be source of truth.

diff --git a/docs/next/state.html b/docs/next/state.html index 7d40713da8b..f3e43be218a 100644 --- a/docs/next/state.html +++ b/docs/next/state.html @@ -80,7 +80,7 @@ )) ), 1000); } - + //state object state = { isShowingText: true }; @@ -110,7 +110,7 @@ // skip this line if using Create React Native App AppRegistry.registerComponent('AwesomeProject', () => BlinkApp); - +

In a real application, you probably won't be setting state with a timer. You might set state when you have new data from the server, or from user input. You can also use a state container like Redux or Mobx to control your data flow. In that case you would use Redux or Mobx to modify your state rather than calling setState directly.

When setState is called, BlinkApp will re-render its Component. By calling setState within the Timer, the component will re-render every time the Timer ticks.

diff --git a/docs/next/state/index.html b/docs/next/state/index.html index 7d40713da8b..f3e43be218a 100644 --- a/docs/next/state/index.html +++ b/docs/next/state/index.html @@ -80,7 +80,7 @@ )) ), 1000); } - + //state object state = { isShowingText: true }; @@ -110,7 +110,7 @@ // skip this line if using Create React Native App AppRegistry.registerComponent('AwesomeProject', () => BlinkApp); - +

In a real application, you probably won't be setting state with a timer. You might set state when you have new data from the server, or from user input. You can also use a state container like Redux or Mobx to control your data flow. In that case you would use Redux or Mobx to modify your state rather than calling setState directly.

When setState is called, BlinkApp will re-render its Component. By calling setState within the Timer, the component will re-render every time the Timer ticks.

TypeRequired