You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updates the bug report and feature request issue templates to give the
community more direction on how to fill them out. Most of the
boilerplate is copied from angular/angular, and this aligns our tone and
organizational style with angular/angular.
<!-- Did this behavior use to work in the previous version? -->
24
+
<!-- βοΈ--> Yes, the previous version in which this bug was not present was: ....
25
+
26
+
### Description
27
+
28
+
<!-- βοΈ--> A clear and concise description of the problem...
13
29
14
30
If the bug is caused or experienced by a particular source code, please provide a minimal
15
31
reproduction of that source code.
16
32
17
-
**To Reproduce**
33
+
## Bug Type
34
+
What does this bug affect
35
+
36
+
<!-- Please check the one that applies to this bug report using "x". -->
37
+
38
+
-[ ] Angular Language Service VSCode extension
39
+
-[ ] Angular Language Service server
40
+
41
+
## Reproduction
18
42
19
43
Steps to reproduce the behavior:
20
44
1. Go to '...'
@@ -26,22 +50,60 @@ Steps to reproduce the behavior:
26
50
27
51
A clear and concise description of what you expected to happen.
28
52
29
-
**Logs**
30
-
31
-
Log file gives us deep insight into the behavior and performance of the extension, so we strongly
32
-
recommend you upload it.
53
+
### **Logs**
33
54
34
-
Go to the command palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows), search `Open Angular Server log`
55
+
Log file gives us deep insight into the behavior and performance of the extension. If the issue is a performance
56
+
problem or an error occured, please provide the output of the log file below.
35
57
36
58
Set Angular Log level to verbose.
37
-
Open settings (File/Preferences/Settings on Windows, Code/Preferences/Settings on Mac), go to Extensions/Angular Language Service, set `angular.log` to `verbose`.
38
59
39
-
**Screenshots**
60
+
<pre><code>
61
+
<!-- If the issue is accompanied by log file output, please share it below.
62
+
63
+
Set the Angular Log level to verbose by opening settings (File/Preferences/Settings on Windows, Code/Preferences/Settings on Mac), go to Extensions/Angular Language Service, set `angular.log` to `verbose`.
64
+
65
+
To open the log file, go to the command palette (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows), search `Open Angular Server log`.
66
+
67
+
Alternatively, if the log file is long, it can be uploaded instead of pasting below. -->
68
+
<!-- βοΈ-->
69
+
70
+
</code></pre>
71
+
72
+
### **Screenshots**
40
73
41
74
If applicable, add screenshots to help explain your problem.
42
75
43
76

44
77
45
-
**Additional context**
78
+
## π Your Environment
79
+
**Angular Version:**
80
+
<pre><code>
81
+
<!-- run `ng version` and paste output below -->
82
+
<!-- βοΈ-->
83
+
84
+
</code></pre>
85
+
86
+
Extension Version:
87
+
<pre><code>
88
+
<!-- Enter the version of 'Angular Language Service'. Example: v11.2.11 -->
89
+
<!-- βοΈ-->
90
+
91
+
</code></pre>
92
+
93
+
VSCode Version:
94
+
<pre><code>
95
+
<!-- Open 'About Visual Studio Code' and paste output below -->
96
+
<!-- βοΈ-->
97
+
98
+
</code></pre>
99
+
100
+
Operating System:
101
+
<pre><code>
102
+
<!-- Example: Windows 10 Version 1703 OS Build 15063.483 -->
103
+
<!-- βοΈ-->
104
+
105
+
</code></pre>
106
+
107
+
**Anything else relevant?**
108
+
<!-- βοΈDo any of these matter hardware, other extensions installed, build environment, ...? If so, please mention it below. -->
0 commit comments