@@ -5,13 +5,12 @@ We work hard to provide a high-quality and useful SDK, and we greatly value
5
5
feedback and contributions from our community. Whether it's a bug report,
6
6
new feature, correction, or additional documentation, we welcome your issues
7
7
and pull requests. Please read through this document before submitting any
8
- [ issues] [ ] or [ pull requests] [ pr ] to ensure we have all the necessary information to
8
+ [ issues] or [ pull requests] [ pr ] to ensure we have all the necessary information to
9
9
effectively respond to your bug report or contribution.
10
10
11
11
Jump To:
12
12
13
13
* [ Bug Reports] ( _#Bug-Reports_ )
14
- * [ Feature Requests] ( _#Feature-Requests_ )
15
14
* [ Code Contributions] ( _#Code-Contributions_ )
16
15
17
16
## How to contribute
@@ -69,18 +68,6 @@ guidelines prior to filing a bug report.
69
68
as well, like whether this is a persistent issue, or if it only occurs
70
69
some of the time.
71
70
72
- ## Feature Requests
73
-
74
- Open an [ issue] [ issues ] with the following:
75
-
76
- * A short, descriptive title. Ideally, other community members should be able
77
- to get a good idea of the feature just from reading the title.
78
- * A detailed description of the the proposed feature.
79
- * Why it should be added to the SDK.
80
- * If possible, example code to illustrate how it should work.
81
- * Use Markdown to make the request easier to read;
82
- * If you intend to implement this feature, indicate that you'd like to the issue to be assigned to you.
83
-
84
71
## Code Contributions
85
72
86
73
We are always happy to receive code and documentation contributions to the SDK.
0 commit comments