-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
React Native CLI - init command support for generating Windows projects #3
Labels
must-have
p1
Milestone
Comments
Not sure why the title of this issue changed. Seems separate. I still think we need a VS extension... |
This is done. |
GantMan
referenced
this issue
in infinitered/react-native-windows
Sep 29, 2016
AsyncStorageModule provides permanent storage for React Native JavaScript applications. - implement PR #3 comments Fixes microsoft#136
GantMan
referenced
this issue
in infinitered/react-native-windows
Sep 29, 2016
AsyncStorageModule provides permanent storage for React Native JavaScript applications. - implement PR #3 comments Fixes microsoft#136
GantMan
referenced
this issue
in infinitered/react-native-windows
Sep 29, 2016
ReactWebView provides access to native webview UI components for React Native JavaScript applications. - PR comments #3 implemented Fixes microsoft#118
kmelmon
added a commit
that referenced
this issue
Jul 23, 2020
* fix smoke test * comment * so far so good, try #3
kmelmon
added a commit
that referenced
this issue
Aug 18, 2020
* re-enable * comment out PlatformColor test, this was the failing test in the past as well * trying again, this time commenting out PanResponder Sample, which comes just before the failing test * trying to wait for home page to load before continuing * another take on waiting for item in FlatList to be loaded first * trying new approach, enter test name in edit box to filter first * made some progress, now timing out on edit control, add polling for that control * finally! success. Try #2 * try #3, fingers crossed! * try #4 * split test into groups * bumping up timeout * try #2 with longer timeout * go back to one testspec * try #4 with longer timeout * try #5 with longer timeout. really folks I think I got it this time :) * convert all the tests to use same mechanism * Change files * remove smoke test * stability pass after removing smoke test, try #2
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Include features like:
The text was updated successfully, but these errors were encountered: