commit | author | age
|
58179b
|
1 |
<!-- |
SE |
2 |
**BEFORE PUBLISHING AN ISSUE** |
|
3 |
|
|
4 |
1) Make sure you are using the latest version of react-datetime. Execute |
|
5 |
npm ls react-datetime |
|
6 |
in your terminal to see what version you are using, and compare it to what verion is published to |
|
7 |
npm by looking at the package's npm page: |
|
8 |
https://www.npmjs.com/package/react-datetime |
|
9 |
|
|
10 |
2) Some of the most frequently asked questions have the answer for them in the documentation. |
|
11 |
Be sure to read through the API carefully before publishing an issue: |
|
12 |
https://github.com/YouCanBookMe/react-datetime#api |
|
13 |
We also use the label *Documentation* for issues that have code examples in them which may be |
|
14 |
useful for other developers, please have a look there as well: |
|
15 |
https://github.com/YouCanBookMe/react-datetime/issues?utf8=%E2%9C%93&q=label%3Adocumentation%20 |
|
16 |
|
|
17 |
3) Discussions for version 3 of react-datetime has been initiated, and we have come up with some |
|
18 |
feature and bug candidates. This means that if a feature or bug has been requested/reported many |
|
19 |
times, it's likely to be a candidate for version 3. Make sure your bug or feature is not included |
|
20 |
in this list before publishing it. |
|
21 |
|
|
22 |
You can find all the candidates here in the *Candidates* column: |
|
23 |
https://github.com/YouCanBookMe/react-datetime/projects/1 |
|
24 |
--> |
|
25 |
|
|
26 |
|
|
27 |
### I'm Submitting a ... |
|
28 |
<!-- Put an "x" in the box for the type of report that apply --> |
|
29 |
``` |
|
30 |
[ ] Bug report |
|
31 |
[ ] Feature request |
|
32 |
[ ] Support request |
|
33 |
``` |
|
34 |
|
|
35 |
### Steps to Reproduce |
|
36 |
<!-- Define the minimal steps to reproduce the bug, preferably in the format of a numbered list --> |
|
37 |
|
|
38 |
### Expected Results |
|
39 |
<!-- Describe what the expected results are --> |
|
40 |
|
|
41 |
### Actual Results |
|
42 |
<!-- Describe what the actual results are --> |
|
43 |
|
|
44 |
### Minimal Reproduction of the Problem |
|
45 |
<!-- |
|
46 |
If the current behavior is a bug or you can illustrate your feature request better with an |
|
47 |
example, please provide a *minimal demo* (if possible) of the problem via |
|
48 |
http://codepen.io/ or similar. We recommend that you fork this example as a starting point, |
|
49 |
it's using the *latest published* version of react-datetime: |
|
50 |
http://codepen.io/simeg/pen/mEmQmP |
|
51 |
--> |
|
52 |
|
|
53 |
### Other Information (e.g. stacktraces, related issues, suggestions how to fix) |
|
54 |
<!-- Any other information you think is valuable can be put here --> |
|
55 |
|
|
56 |
|
|
57 |
<!-- |
|
58 |
Is there anything in this template you think is confusing, unclear, redundant or just simply bad? |
|
59 |
Please let us know either via creating an issue or creating a PR with changes to it. |
|
60 |
--> |