mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
@@ -48,7 +48,7 @@
|
||||
<p>Even if the feature does belong in the core library, adding it means maintaining it. A maintainer will encourage you to submit a pull request or otherwise post your request to <a href="https://react-native.canny.io/feature-requests">Canny</a>.</p>
|
||||
<p>An exception can be made for proposals and long-running discussions, though these should be rare. If you have been contributing to the project long enough, you will probably already have access to the <a href="https://www.facebook.com/groups/reactnativeoss/">React Native Core Contributors</a> Facebook Group, where this sort of discussion is usually held.</p></li>
|
||||
<li><p><strong>Is this issue a request for help?</strong></p>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="stackoverflow.com/questions/tagged/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<p>Questions should absolutely be asked on Stack Overflow rather than GitHub. Maintainers should encourage contributors to ask on Stack Overflow, before closing the issue. Feel free to also answer some <a href="https://stackoverflow.com/tags/react-native">questions on Stack Overflow</a>, you'll get rep!</p></li>
|
||||
<li><p><strong>Was the <a href="https://github.com/facebook/react-native/blob/master/.github/ISSUE_TEMPLATE.md">Issue Template</a> used to fill out the issue? Did the author answer Yes to both questions at the top?</strong></p>
|
||||
<p>If not, the maintainer will ask you to provide more information by filling out the issue template, then they will close the issue.</p></li>
|
||||
<li><p><strong>Is the issue a duplicate of an existing, open issue?</strong></p>
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Reference in New Issue
Block a user