@@ -17,23 +17,25 @@ Issues are organized in terms of components.
1717Issue titles should include the name of the component as a tag
1818at the very beginning. Consider the following titles:
1919
20- Bad: ` Fix input field padding of search bar `
21- Good: ` [SearchBar] Fix input field padding `
20+ * Bad: ` Fix input field padding of search bar `
21+ * Good: ` [SearchBar] Fix input field padding `
2222
2323or
2424
25- Bad: ` Add information about titles to documentation `
26- Good: ` [Docs] Add information about titles `
25+ * Bad: ` Add information about titles to documentation `
26+ * Good: ` [Docs] Add information about titles `
2727
2828Some common tags include:
29- | Editor| SecondaryPanes| UI| Other|
30- | ----------| ------| -----| ----|
31- | Editor| CommandBar| SourceTree| Accessibility|
32- | SourceTabs| WatchExpressions| TextSearch| Theme|
33- | SearchBar| Breakpoints| WelcomeBox| Reducer|
34- | SourceFooter| CallStack|| Action|
29+
30+ | Editor| SecondaryPanes| UI| Other|
31+ | ----------| ------| -----| ----|
32+ | Editor| CommandBar| SourceTree| Accessibility|
33+ | SourceTabs| WatchExpressions| TextSearch| Theme|
34+ | SearchBar| Breakpoints| WelcomeBox| Reducer|
35+ | SourceFooter| CallStack|| Action|
3536|| Scopes|| Docs| RTL|
3637
38+
3739** User Perspective**
3840
3941The best issue titles are framed in terms of the impact on the user. i.e.
0 commit comments