Skip to content

Commit df1d570

Browse files
authored
Add Issue Templates (#760)
* issue template * Update ---getting-help.md
1 parent 9e198b3 commit df1d570

File tree

4 files changed

+135
-0
lines changed

4 files changed

+135
-0
lines changed
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: "\U0001F4A1 Feature request"
3+
about: Suggest an idea for this project
4+
5+
---
6+
7+
**Is your feature request related to a problem? Please describe.**
8+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
9+
10+
**Describe the solution you'd like**
11+
A clear and concise description of what you want to happen.
12+
13+
**Describe alternatives you've considered**
14+
A clear and concise description of any alternative solutions or features you've considered.
15+
16+
**Additional context**
17+
Add any other context or screenshots about the feature request here.
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
---
2+
name: "🙋‍Getting Help"
3+
about: Join https://community.parseplatform.org
4+
5+
---
6+
7+
<!---
8+
9+
**We use GitHub Issues for reporting bugs with Parse JS SDK.**
10+
11+
If you have a code-level question, use Stack Overflow with tags `parse-platform` and `parse-javascript-sdk`
12+
13+
If you have a non-bug question, you should join the [Parse Community's Discourse forum](https://community.parseplatform.org/c/sdk/js).
14+
15+
--->
Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
---
2+
name: "\U0001F525 Parse SDK JS 2.0.0"
3+
about: Report an issue while migrating to Parse SDK JS 2.0.0
4+
5+
---
6+
7+
<!---
8+
** Use this template only if you have an issue migrating to Parse SDK JS 2.0.0 **
9+
10+
If you have a question, ask on [Parse Community's Discourse forum](https://community.parseplatform.org/c/sdk/js)
11+
12+
If you have a vulnerability disclosure, please follow our policy available here https://github.com/parse-community/parse-server/blob/master/SECURITY.md
13+
14+
You may also search through existing issues before opening a new one: https://github.com/parse-community/Parse-SDK-JS/issues
15+
16+
--- Please use this template. If you don't use this template, your issue may be closed without comment. ---
17+
--->
18+
19+
# Before opening the issue please ensure that you have:
20+
21+
- [ ] [Read the migration guide](https://github.com/parse-community/parse-server/blob/master/3.0.0.md) to parse-server 3.0.0
22+
- [ ] [Read the migration guide](https://github.com/parse-community/Parse-SDK-JS/blob/master/2.0.0.md) to Parse SDK JS 2.0.0
23+
24+
### Issue Description
25+
26+
<!--- Describe your issue in as much detail as possible. -->
27+
28+
### Steps to reproduce
29+
30+
<!--- Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable. --->
31+
32+
### Expected Results
33+
34+
<!--- What you expected to happen. --->
35+
36+
### Actual Outcome
37+
38+
<!--- What is happening instead. --->
39+
40+
### Environment Setup
41+
42+
- **Server**
43+
- parse-server version (Be specific! Don't say 'latest'.) : [FILL THIS OUT]
44+
- Operating System: [FILL THIS OUT]
45+
- Hardware: [FILL THIS OUT]
46+
- Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]
47+
48+
- **JS SDK**
49+
- JS SDK version: [FILL THIS OUT]
50+
- Application? (Browser, Node, React-Native, etc): [FILL THIS OUT]
51+
52+
### Logs/Trace
53+
54+
<!--- Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment. --->
Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
---
2+
name: "\U0001F41B Report an issue"
3+
about: Report an issue on Parse JS SDK
4+
5+
---
6+
7+
<!---
8+
9+
**We use GitHub Issues for reporting bugs with Parse JS SDK.**
10+
11+
If you have a *question*, you should join the [Parse Community's Discourse forum](https://community.parseplatform.org/c/sdk/js).
12+
13+
If you have a vulnerability disclosure, please follow our policy available here https://github.com/parse-community/parse-server/blob/master/SECURITY.md
14+
15+
You may also search through existing issues before opening a new one: https://github.com/parse-community/Parse-SDK-JS/issues
16+
17+
--- Please use this template. If you don't use this template, your issue may be closed without comment. ---
18+
--->
19+
### Issue Description
20+
21+
<!--- Describe your issue in as much detail as possible. -->
22+
23+
### Steps to reproduce
24+
25+
<!--- Please include a detailed list of steps that reproduce the issue. Include curl commands when applicable. --->
26+
27+
### Expected Results
28+
29+
<!--- What you expected to happen. --->
30+
31+
### Actual Outcome
32+
33+
<!--- What is happening instead. --->
34+
35+
### Environment Setup
36+
37+
- **Server**
38+
- parse-server version (Be specific! Don't say 'latest'.) : [FILL THIS OUT]
39+
- Operating System: [FILL THIS OUT]
40+
- Hardware: [FILL THIS OUT]
41+
- Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): [FILL THIS OUT]
42+
43+
- **JS SDK**
44+
- JS SDK version: [FILL THIS OUT]
45+
- Application? (Browser, Node, React-Native, etc): [FILL THIS OUT]
46+
47+
### Logs/Trace
48+
49+
<!--- Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment. --->

0 commit comments

Comments
 (0)