Skip to content

Commit 072283d

Browse files
authored
Add issue templates for feature and module requests (#530)
* Create feature-request template * Rename feature-request.md to feature_request.md * Create module_request.md
1 parent 3ea5e7d commit 072283d

File tree

2 files changed

+62
-0
lines changed

2 files changed

+62
-0
lines changed
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
name: React Native for macOS feature request
3+
about: Suggest a new feature or idea
4+
title: Your feature request
5+
labels: Proposal
6+
assignees: ''
7+
8+
---
9+
10+
<!-- This is a template for new feature or API proposals for React Native for macOS. Use this to submit new API/component requests or behavior updates that are specific to macOS-only.
11+
- For feature requests to React Native, go [here](https://github.com/react-native-community/discussions-and-proposals).
12+
- For feature requests to React Native for Windows (or) Desktop features in general, go [here](https://github.com/microsoft/react-native-windows/issues/new?assignees=&labels=Proposal&template=react-native-windows--vnext--feature-request.md&title=Your+feature+request).
13+
-->
14+
15+
# Proposal: [your title here]
16+
<!-- Add a title for your feature or API proposal. Please be short and descriptive -->
17+
18+
## Summary
19+
<!-- Brief explanation of the new API or change. -->
20+
21+
## Motivation
22+
23+
<!-- Why are we doing this? What use cases does it support? What is the expected outcome? Why should this be done for macOS-only?
24+
25+
Please focus on explaining the motivation so that if this proposal is not accepted, the motivation could be used to develop alternative solutions. In other words, enumerate the constraints you are trying to solve without coupling them too closely to the solution you have in mind. -->
26+
27+
## Basic example
28+
29+
<!-- [Optional] If the proposal involves a new or changed API, include a basic code example. Omit this section if it's not applicable. -->
30+
31+
## Open Questions
32+
33+
<!-- Please list any open issues that you think still need to be addressed.
34+
These could include areas you think would benefit from community or the react-native-windows team input -->
Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
---
2+
name: React Native for macOS Community Module support request
3+
about: Suggest that React Native for macOS support be added to a community module
4+
title: Support react-native-foo
5+
labels: Extensions
6+
assignees: ''
7+
8+
---
9+
10+
<!-- This Issue template helps us track which modules need to work with React Native for macOS. If you have found a community module that doesn't yet work with React Native for macOS, fill out the Issue fields below! -->
11+
12+
# Support `react-native-foo` on React Native for macOS
13+
<!-- Update the react-native-foo text with the module name -->
14+
15+
## Basic Info
16+
- Module Repo URL: [link to repo]()
17+
- Target version:
18+
- [ ] Issue exists on module repo (if so, [link]())
19+
<!-- If the community module repo already has an issue tracking adding React Native Support, please check this box and link to it. -->
20+
21+
## Which app/customer is requesting this module?
22+
<!-- Please describe which app/customer needs this module. -->
23+
24+
## In what scenarios will this module be used?
25+
<!-- Please detail how the app/customer will use the module. Please include screenshots/mockups/wireframes if possible. -->
26+
27+
## Essential Features
28+
<!-- Please enumerate which features of the module are required. For example, you may be using a map module and you only need the 'pinning' functionality and NOT the turn-by-turn direction functionality. -->

0 commit comments

Comments
 (0)