Changes between Version 14 and Version 15 of DevNotes/DevGuide/CodingRules
- Timestamp:
- May 30, 2016 8:00:04 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevNotes/DevGuide/CodingRules
v14 v15 26 26 * API interface (to be included in the future) 27 27 28 Golden Rule: 28 == Golden Rule: == 29 29 30 30 '''The committed code should NEVER break the build.''' 31 31 '''If you do break the build - the no. 1 priority is to fix it IMMEDIATELY.''' 32 32 33 Coding Standards 33 == Coding Standards == 34 34 35 35 Docstring … … 148 148 * Use inline comments (sparingly) to clarify confusing lines. 149 149 150 Testing 150 == Testing == 151 151 152 152 * Unit tests should test one method only. This allows you to easily identify what failed if the test fails. … … 162 162 * Models: Remember to test a model for critical values (e.g. q=0) 163 163 164 GIT 164 == GIT == 165 165 166 166 * Remember to add files using git add before committing your changes. … … 169 169 * When merging a branch with multiple commits use --squash or interactively rebase before pushing to master. 170 170 171 Code Reviews 171 == Code Reviews == 172 172 173 173 * Code reviews by another developer are encouraged for minor functionality and required for major changes … … 182 182 7. Verify that the defects are actually fixed 183 183 184 Editors 184 == Editors == 185 185 186 186 * Tips and tricks of how to make your life easier when developing code with your favorite editor. … … 192 192 * Both PyCharm and VS allow source level debugging both of self-spawned processes and by attaching to an already running process. 193 193 194 API 194 == API == 195 195 196 196 The proposed access to the core functionality should be consistent for all perspectives and straightforward to use.