Formatting: Difference between revisions
Appearance
Created page with "== 2026 07 31 == What format do we use to name things? - Using "→*" then " * " then ": " to write comments - Method names: Upper Snake Case - Struct names: Upper Snake Case, append "_t" - Variables: Lower Snake Case - Files: - .c, .h, .txt Lowercase with underscores - .txt and .json Upper Camel Case - Folders: By vibes" |
No edit summary |
||
| Line 9: | Line 9: | ||
- .txt and .json Upper Camel Case | - .txt and .json Upper Camel Case | ||
- Folders: By vibes | - Folders: By vibes | ||
Commit formatting: | |||
- https://gist.github.com/qoomon/5dfcdf8eec66a051ecd85625518cfd13 | |||
- <type>(<optional scope>): <description> | |||
- Common Types: | |||
- feat: commits that add or adjust a feature | |||
- fix | |||
- refactor | |||
- style: formatting stuff that does not affect | |||
- test: stuff to do with unit testing | |||
- docs | |||
- build: stuff relating to build frameworks and tools | |||
Revision as of 13:13, 31 July 2026
2026 07 31
What format do we use to name things?
- Using "/**" then " * " then " */" to write comments
- Method names: Upper Snake Case
- Struct names: Upper Snake Case, append "_t"
- Variables: Lower Snake Case
- Files:
- .c, .h, .txt Lowercase with underscores
- .txt and .json Upper Camel Case
- Folders: By vibes
Commit formatting:
- https://gist.github.com/qoomon/5dfcdf8eec66a051ecd85625518cfd13 - <type>(<optional scope>): <description> - Common Types: - feat: commits that add or adjust a feature - fix - refactor - style: formatting stuff that does not affect - test: stuff to do with unit testing - docs - build: stuff relating to build frameworks and tools