1 | ---
|
2 | name: Bug report
|
3 | about: Create a report to help us improve
|
4 | labels: bug
|
5 |
|
6 | ---
|
7 |
|
8 |
|
9 |
|
10 | HELP US HELP YOU, PLEASE
|
11 | - Do a quick search to avoid duplicate issues
|
12 | - Provide as much information as possible (reproduction sandbox, use case for features, etc.)
|
13 | - Consider using a more suitable venue for questions such as Stack Overflow, Gitter, etc.
|
14 |
|
15 | Please fill in the *entire* template below.
|
16 |
|
17 | -->
|
18 |
|
19 | ## Steps to reproduce
|
20 |
|
21 |
|
22 |
|
23 | ## Current Behavior
|
24 |
|
25 |
|
26 |
|
27 | ## Expected Behavior
|
28 |
|
29 |
|
30 |
|
31 | ## Link to reproduction sandbox
|
32 |
|
33 |
|
34 | See https://loopback.io/doc/en/contrib/Reporting-issues.html#loopback-3x-bugs
|
35 | Note: Failure to provide a sandbox application for reproduction purposes will result in the issue being closed.
|
36 | -->
|
37 |
|
38 | ## Additional information
|
39 |
|
40 |
|
41 | Copy+paste the output of these two commands:
|
42 | node -e 'console.log(process.platform, process.arch, process.versions.node)'
|
43 | npm ls --prod --depth 0 | grep loopback
|
44 | -->
|
45 |
|
46 | ## Related Issues
|
47 |
|
48 |
|
49 |
|
50 | _See [Reporting Issues](http://loopback.io/doc/en/contrib/Reporting-issues.html) for more tips on writing good issues_
|