|
| 1 | +# Welcome! Thank you for contributing to myleetcode! |
| 2 | + |
| 3 | +We follow the standard GitHub [fork & pull](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests#fork--pull) approach to pull requests. |
| 4 | + |
| 5 | +This project now provides a LeetCode solution in two languages, and you can provide another language solution for LeetCode if you like. But to maintain a good style, your code must meet the requirements of this project. |
| 6 | + |
| 7 | +## Package Path |
| 8 | + |
| 9 | + Now `myleetcode` project structure is: |
| 10 | + |
| 11 | +- myleetcode: |
| 12 | + - `codes` |
| 13 | + - `images` |
| 14 | + - `.gitignore` |
| 15 | + - `.travis.yml` |
| 16 | + - `LICENSE` |
| 17 | + - `README.md` |
| 18 | + - `_config.yml` |
| 19 | + |
| 20 | +All solutions of LeetCode, must be created in package of `codes`. |
| 21 | + |
| 22 | +## Code style |
| 23 | + |
| 24 | +### Java |
| 25 | + |
| 26 | +- Class Name: Start with `_`, and spell problem number in LeetCode. |
| 27 | +- Method Name: Initial in lowercase, then follow hump format. |
| 28 | + |
| 29 | +### Python |
| 30 | + |
| 31 | +- Class Name: Start with `_`, and spell problem number in LeetCode. |
| 32 | +- Method Name: Initial in lowercase, then spell with `_`, if method name have more than one word. |
| 33 | + |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | + |
| 38 | + |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | + |
| 47 | + |
0 commit comments