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
Whether you want to report a bug, an enhancement, a new data structure, or a new algorithm implementation please make sure you check out the issues first, someone might have started working on a similar idea already. If you are sure that what you want to contribute is new, then please open an issue describing what you want to accomplish before you decide to commit any code. This will guarantee no one else will work on the same file(s), data structure and/or algorithm you are working on.
26
+
Please make sure you check out the issues first, someone might have started working on a similar idea already. If you are sure that what you want to contribute is new, then please open an issue describing what you want to implement before you decide to submit a PR.
27
27
28
-
It would be great if you can check out the existing [Issue Templates](ISSUE_TEMPLATE)which outline different types of contributions and how to submit them.
28
+
Please refer to the [Issue Templates](ISSUE_TEMPLATE)to see the different types of contributions.
29
29
30
-
## Coding Conventions:
30
+
## Submitting a Pull Requests
31
31
32
-
The coding conventions are the official Microsoft C# Coding Conventions. Most of the official code styling is supported by default on Visual Studio, but you need to set it up as a policy on Xamarian Studio via the Solution/Project properties window, in case you are using Xamarian Studio.
32
+
After you commit your code, please submit your changes with a pull-request, you can do this on GitHub or through git. Please make sure to refer to the [Pull Request Guideline](PULL_REQUEST_TEMPLATE.md) when creating a new one.
33
+
34
+
## Coding Conventions
35
+
36
+
We follow the official Microsoft C# Coding Conventions (see: below). Most of the styleguide is supported by default on Visual Studio, but you need to set it up as a policy from the Solution/Project properties window, in case you are using Visual Studio Community.
37
+
38
+
Please refer to the following guidelines:
33
39
34
-
Please refer to the [Framework Design Guidelines](https://msdn.microsoft.com/en-us/library/ms229042(v=vs.110).aspx) document on MSDN.
If your implementation depends on a 3rd party library, and you think it is critical, then please communicate this before you change the solution/projects references. We are striving to provide a bare-bones library of data structures and algorithms.
39
46
@@ -45,7 +52,3 @@ You should write a test for every data structure and algorithm you implement. Th
45
52
46
53
*`AlgorithmsTests`: Package hosting unit tests for the Algorithms project.
47
54
*`DataStructuresTests`: Package hosting unit tests for the Data Structures project.
48
-
49
-
## Submitting a Pull Request
50
-
51
-
After you commit your code, please submit your changes with a pull-request, you can do this on GitHub or through git. Please make sure to refer to the [Pull Request Guideline](PULL_REQUEST_TEMPLATE.md) when creating a new one.
0 commit comments