From 966be13fcde3f4e4e2b3a16b3d933711a6c44685 Mon Sep 17 00:00:00 2001
From: Website Deployment Script
Date: Wed, 4 Jan 2017 15:22:53 +0000
Subject: [PATCH] Updated docs for next
---
releases/next/docs/image.html | 2 +-
releases/next/versions.html | 2 +-
versions.html | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/releases/next/docs/image.html b/releases/next/docs/image.html
index 81a8f76b2e3..82c4dd46078 100644
--- a/releases/next/docs/image.html
+++ b/releases/next/docs/image.html
@@ -108,7 +108,7 @@ loaded or downloaded, after which it will be cached. This means that in
principle you could use this method to preload images, however it is not
optimized for that purpose, and may in future be implemented in a way that
does not fully load/download the image data. A proper, supported way to
-preload images will be provided as a separate API.
Parameters:
Name and Type
Description
uri
string
The location of the image.
success
function
The function that will be called if the image was sucessfully found and width
+preload images will be provided as a separate API.
Parameters:
Name and Type
Description
uri
string
The location of the image.
success
function
The function that will be called if the image was successfully found and width
and height retrieved.
failure
function
The function that will be called if there was an error, such as failing to
to retrieve the image.
React Native follows a monthly release train. Every month, a new branch created off master enters the Release Candidate phase, and the previous Release Candidate branch is released and considered stable.
This is the version that is configured automatically when you run react-native init. We highly recommend using the current version of React Native when starting a new project.
If you have an existing project that uses React Native, read the release notes to learn about new features and fixes. You can follow our guide to upgrade your app to the latest version.
For those who live on the bleeding edge. Only recommended if you're actively contributing code to React Native, or if you need to verify how your application behaves in an upcoming release.
You can find past versions of React Native on GitHub. The release notes can be useful if you would like to learn when a specific feature or fix was released.
You can also view the docs for a particular version of React Native by clicking on the Docs link next to the release in this page. You can come back to this page and switch the version of the docs you're reading at any time by clicking on the version number at the top of the page.
React Native follows a monthly release train. Every month, a new branch created off master enters the Release Candidate phase, and the previous Release Candidate branch is released and considered stable.
This is the version that is configured automatically when you run react-native init. We highly recommend using the current version of React Native when starting a new project.
If you have an existing project that uses React Native, read the release notes to learn about new features and fixes. You can follow our guide to upgrade your app to the latest version.
For those who live on the bleeding edge. Only recommended if you're actively contributing code to React Native, or if you need to verify how your application behaves in an upcoming release.
You can find past versions of React Native on GitHub. The release notes can be useful if you would like to learn when a specific feature or fix was released.
You can also view the docs for a particular version of React Native by clicking on the Docs link next to the release in this page. You can come back to this page and switch the version of the docs you're reading at any time by clicking on the version number at the top of the page.
React Native follows a monthly release train. Every month, a new branch created off master enters the Release Candidate phase, and the previous Release Candidate branch is released and considered stable.
This is the version that is configured automatically when you run react-native init. We highly recommend using the current version of React Native when starting a new project.
If you have an existing project that uses React Native, read the release notes to learn about new features and fixes. You can follow our guide to upgrade your app to the latest version.
For those who live on the bleeding edge. Only recommended if you're actively contributing code to React Native, or if you need to verify how your application behaves in an upcoming release.
You can find past versions of React Native on GitHub. The release notes can be useful if you would like to learn when a specific feature or fix was released.
You can also view the docs for a particular version of React Native by clicking on the Docs link next to the release in this page. You can come back to this page and switch the version of the docs you're reading at any time by clicking on the version number at the top of the page.
React Native follows a monthly release train. Every month, a new branch created off master enters the Release Candidate phase, and the previous Release Candidate branch is released and considered stable.
This is the version that is configured automatically when you run react-native init. We highly recommend using the current version of React Native when starting a new project.
If you have an existing project that uses React Native, read the release notes to learn about new features and fixes. You can follow our guide to upgrade your app to the latest version.
For those who live on the bleeding edge. Only recommended if you're actively contributing code to React Native, or if you need to verify how your application behaves in an upcoming release.
You can find past versions of React Native on GitHub. The release notes can be useful if you would like to learn when a specific feature or fix was released.
You can also view the docs for a particular version of React Native by clicking on the Docs link next to the release in this page. You can come back to this page and switch the version of the docs you're reading at any time by clicking on the version number at the top of the page.