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
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/bug_report.md
+25-16Lines changed: 25 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,23 +4,26 @@ about: Create a report to help us fix something that isn't working as expected
4
4
title: ''
5
5
labels: "bug :bug:"
6
6
assignees: ''
7
-
8
7
---
9
8
10
9
<!-- 🚨 PLEASE DO NOT SKIP ANY INSTRUCTIONS AND INFORMATION MENTIONED BELOW AS THEY ARE ALL REQUIRED AND ESSENTIAL TO INVESTIGATE THE ISSUE. ISSUES WITH MISSING INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION
11
10
...
12
-
IF NOT CERTAIN ABOUT THE ISSUE AND REQUIRE MORE CLARITY THEN PLEASE POST ON "QUESTIONS & HELP" CATEGORY OF THE DISCUSSIONS PLATFORM [https://github.com/CommunityToolkit/WindowsCommunityToolkit/discussions/categories/questions-help] WHERE YOU CAN DISCUSS AND ENAGAGE WITH THE COMMUNITY TO GAIN FURTHER CLAIRITY REGARDING THE ISSUE 🚨 -->
11
+
IF NOT CERTAIN ABOUT THE ISSUE AND REQUIRE MORE CLARITY THEN PLEASE POST ON "QUESTIONS & HELP" CATEGORY OF THE DISCUSSIONS PLATFORM [https://github.com/CommunityToolkit/WindowsCommunityToolkit/discussions/categories/questions-help] WHERE YOU CAN DISCUSS AND ENGAGE WITH THE COMMUNITY TO GAIN FURTHER CLARITY REGARDING THE ISSUE 🚨 -->
13
12
14
13
## Describe the bug
14
+
15
15
A clear and concise description of what the bug is.
16
16
17
17
-[ ] Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:
18
18
19
19
## Steps to Reproduce
20
20
21
-
-[ ] Can this be reproduced in the Sample App? (Either in a sample as-is or with new XAML pasted in the editor.) If so, please provide custom XAML or steps to reproduce. If not, let us know why it can't be reproduced (e.g. more complex setup, environment, dependencies, etc...) <!-- Being able to reproduce the problem in the sample app, really stream-lines the whole process in being able to discover, resolve, and validate bug fixes. -->
21
+
-[ ] Can this be reproduced in the Sample App? (Either in a sample as-is or with new XAML pasted in the editor.) If so, please provide custom XAML or steps to reproduce. If not, let us know why it can't be reproduced (e.g. more complex setup, environment, dependencies, etc...)
22
+
23
+
<!-- Being able to reproduce the problem in the sample app, really stream-lines the whole process in being able to discover, resolve, and validate bug fixes. -->
22
24
23
25
Steps to reproduce the behavior:
26
+
24
27
1. Given the following environment (Sample App w/ XAML, Project with Isolated setup, etc...)
25
28
2. Go to '...'
26
29
3. Click on '....'
@@ -30,46 +33,52 @@ Steps to reproduce the behavior:
30
33
<!-- Provide as many code-snippets or XAML snippets where appropriate. -->
31
34
32
35
## Expected behavior
33
-
A clear and concise description of what you expected to happen.
36
+
37
+
<!-- A clear and concise description of what you expected to happen. -->
34
38
35
39
## Screenshots
36
-
If applicable, add screenshots to help explain your problem.
40
+
41
+
<!-- If applicable, add screenshots to help explain your problem. -->
37
42
38
43
## Environment
39
-
<!-- Check one or more of the following options with "x" -->
40
-
```
41
-
NuGet Package(s):
44
+
45
+
<!-- Check one or more of the following options with "x" and replace the {build_number} and {minor_version} with the actual values -->
46
+
47
+
NuGet Package(s): <!-- Which NuGet Packages have you used -->
42
48
43
49
Package Version(s):
44
50
45
51
Windows 10 Build Number:
52
+
46
53
-[ ] Fall Creators Update (16299)
47
54
-[ ] April 2018 Update (17134)
48
55
-[ ] October 2018 Update (17763)
49
56
-[ ] May 2019 Update (18362)
50
57
-[ ] May 2020 Update (19041)
51
-
- [ ] Insider Build (build number: )
58
+
-[ ] Insider Build ({build_number})
52
59
53
60
App min and target version:
61
+
54
62
-[ ] Fall Creators Update (16299)
55
63
-[ ] April 2018 Update (17134)
56
64
-[ ] October 2018 Update (17763)
57
65
-[ ] May 2019 Update (18362)
58
66
-[ ] May 2020 Update (19041)
59
-
- [ ] Insider Build (xxxxx)
67
+
-[ ] Insider Build ({build_number})
60
68
61
69
Device form factor:
70
+
62
71
-[ ] Desktop
63
72
-[ ] Xbox
64
73
-[ ] Surface Hub
65
74
-[ ] IoT
66
75
67
-
Visual Studio
68
-
- [ ] 2017 (version: )
69
-
- [ ] 2019 (version: )
70
-
- [ ] 2019 Preview (version: )
76
+
Visual Studio version:
71
77
72
-
```
78
+
-[ ] 2017 (15.{minor_version})
79
+
-[ ] 2019 (16.{minor_version})
80
+
-[ ] 2022 (17.{minor_version})
73
81
74
82
## Additional context
75
-
Add any other context about the problem here.
83
+
84
+
<!-- Add any other context about the problem here. -->
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/feature_request.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,27 +4,27 @@ about: I have a new idea or improvement for the toolkit
4
4
title: "[Feature]"
5
5
labels: "feature request :mailbox_with_mail:"
6
6
assignees: ''
7
-
8
7
---
9
8
10
9
<!-- 🚨 PLEASE PROVIDE DETAILED INFORMATION AND DO NOT SKIP ANY INSTRUCTIONS AND INFORMATION MENTIONED BELOW AS THEY ARE ALL REQUIRED AND ESSENTIAL TO HELP US UNDERSTAND THE FEATURE.
11
10
...
12
-
IF NOT CERTAIN ABOUT THE FEATURE AND REQUIRE MORE CLARITY THEN PLEASE POST ON "IDEAS" CATEGORY OF THE DISCUSSIONS PLATFORM [https://github.com/CommunityToolkit/WindowsCommunityToolkit/discussions/categories/ideas] WHERE YOU CAN DISCUSS AND ENAGAGE WITH THE COMMUNITY TO GAIN FURTHER CLAIRITY REGARDING THE FEATURE 🚨 -->
11
+
IF NOT CERTAIN ABOUT THE FEATURE AND REQUIRE MORE CLARITY THEN PLEASE POST ON "IDEAS" CATEGORY OF THE DISCUSSIONS PLATFORM [https://github.com/CommunityToolkit/WindowsCommunityToolkit/discussions/categories/ideas] WHERE YOU CAN DISCUSS AND ENGAGE WITH THE COMMUNITY TO GAIN FURTHER CLARITY REGARDING THE FEATURE 🚨 -->
13
12
14
13
## Describe the problem this feature would solve
14
+
15
15
<!-- Please describe or link to any existing issues or discussions.
16
16
A clear and concise description of what the problem is, starting with the user story.
17
17
Provide examples of the restrictions in the current environment that hinders the work your users or you want to perform. What are the ways this new feature will help transform and deliver those results?
18
18
For example, I am currently using the InfiniteCanvas control which lacks the TabbedCommandBar control feature. I am looking to improve user experience therefore i would like to use that in my project to provide ease of accessibility and a user-friendly interface. This new feature will provide quick access to the toolbar, enhance space utilization, etc [...] -->
19
19
20
-
21
20
## Describe the solution
22
-
<!-- A clear and concise description of what you want to happen. Define how do you think it will help the community and adds value to the toolkit? -->
23
21
22
+
<!-- A clear and concise description of what you want to happen. Define how do you think it will help the community and adds value to the toolkit? -->
24
23
25
24
## Describe alternatives you've considered
26
-
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
27
25
26
+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
28
27
29
28
## Additional context & Screenshots
29
+
30
30
<!-- Add any other context or screenshots about the feature request here.-->
<!-- 🚨 Please Do Not skip any instructions and information mentioned below as they are all required and essential to evaluate and test the PR. By fulfilling all the required information you will be able to reduce the volume of questions and most likely help merge the PR faster 🚨 -->
2
2
3
-
<!-- 👉 It is imperative to resolve ONE ISSUE PER PR and avoid making multiple changes unless the changes interrelate with each other -->
3
+
<!-- 👉 It is imperative to resolve ONE ISSUE PER PR and avoid making multiple changes unless the changes interrelate with each other -->
4
4
5
5
<!-- 📝 Please always keep the "☑️ Allow edits by maintainers" button checked in the Pull Request Template as it increases collaboration with the Toolkit maintainers by permitting commits to your PR branch (only) created from your fork. This can let us quickly make fixes for minor typos or forgotten StyleCop issues during review without needing to wait on you doing extra work. Let us help you help us! 🎉 -->
6
6
7
+
## Fixes
7
8
8
-
## Fixes #
9
-
<!-- Add the relevant issue number after the "#" mentioned above (for ex: "## Fixes #1234") which will automatically close the issue once the PR is merged. -->
9
+
<!-- Add the relevant issue number after the word "Fixes" mentioned above (for ex: "## Fixes #1234") which will automatically close the issue once the PR is merged. -->
10
10
11
11
<!-- Add a brief overview here of the feature/bug & fix. -->
12
12
13
13
## PR Type
14
+
14
15
What kind of change does this PR introduce?
16
+
15
17
<!-- Please uncomment one or more options below that apply to this PR. -->
16
18
17
19
<!-- - Bugfix -->
@@ -23,30 +25,30 @@ What kind of change does this PR introduce?
23
25
<!-- - Sample app changes -->
24
26
<!-- - Other... Please describe: -->
25
27
26
-
27
28
## What is the current behavior?
28
-
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
29
29
30
+
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
30
31
31
32
## What is the new behavior?
32
-
<!-- Describe how was this issue resolved or changed? -->
33
33
34
+
<!-- Describe how was this issue resolved or changed? -->
34
35
35
36
## PR Checklist
36
37
37
-
Please check if your PR fulfills the following requirements:
38
+
Please check if your PR fulfills the following requirements:<!-- and remove the ones that are not applicable to the current PR -->
38
39
39
-
-[ ] Tested code with current [supported SDKs](../readme.md#supported)
40
-
-[ ] Pull Request has been submitted to the documentation repository [instructions](..\contributing.md#docs). Link: <!-- docs PR link -->
40
+
-[ ] Tested code with current [supported SDKs](../#supported)
41
+
-[ ] Pull Request has been submitted to the documentation repository [instructions](../blob/main/Contributing.md#docs). Link: <!-- docs PR link -->
41
42
-[ ] Sample in sample app has been added / updated (for bug fixes / features)
42
-
-[ ] Icon has been created (if new sample) following the [Thumbnail Style Guide and templates](https://github.com/CommunityToolkit/WindowsCommunityToolkit-design-assets)
43
+
-[ ] Icon has been created (if new sample) following the [Thumbnail Style Guide and templates](https://github.com/CommunityToolkit/WindowsCommunityToolkit-design-assets)
43
44
-[ ] New major technical changes in the toolkit have or will be added to the [Wiki](https://github.com/CommunityToolkit/WindowsCommunityToolkit/wiki) e.g. build changes, source generators, testing infrastructure, sample creation changes, etc...
44
45
-[ ] Tests for the changes have been added (for bug fixes / features) (if applicable)
45
-
-[ ] Header has been added to all new source files (run *build/UpdateHeaders.bat*)
46
+
-[ ] Header has been added to all new source files (run _build/UpdateHeaders.bat_)
46
47
-[ ] Contains **NO** breaking changes
47
48
48
49
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below.
49
-
Please note that breaking changes are likely to be rejected within minor release cycles or held until major versions. -->
50
-
50
+
Please note that breaking changes are likely to be rejected within minor release cycles or held until major versions. -->
51
51
52
52
## Other information
53
+
54
+
<!-- Please add any other information that might be helpful to reviewers. -->
0 commit comments