@@ -5,13 +5,12 @@ We work hard to provide a high-quality and useful SDK, and we greatly value
55feedback and contributions from our community. Whether it's a bug report,
66new feature, correction, or additional documentation, we welcome your issues
77and 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
99effectively respond to your bug report or contribution.
1010
1111Jump To:
1212
1313* [ Bug Reports] ( _#Bug-Reports_ )
14- * [ Feature Requests] ( _#Feature-Requests_ )
1514* [ Code Contributions] ( _#Code-Contributions_ )
1615
1716## How to contribute
@@ -69,18 +68,6 @@ guidelines prior to filing a bug report.
6968 as well, like whether this is a persistent issue, or if it only occurs
7069 some of the time.
7170
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-
8471## Code Contributions
8572
8673We are always happy to receive code and documentation contributions to the SDK.
0 commit comments