https://github.com/yelmuratoff/katas

Solving coding katas in Dart language using TDD
https://github.com/yelmuratoff/katas

coding-katas dart kata katas tdd

Last synced: about 1 month ago
JSON representation

Solving coding katas in Dart language using TDD

• Host: GitHub
• URL: https://github.com/yelmuratoff/katas
• Owner: yelmuratoff
• Created: 2024-04-25T20:29:42.000Z (10 months ago)
• Default Branch: main
• Last Pushed: 2024-05-15T19:26:19.000Z (9 months ago)
• Last Synced: 2024-12-24T20:14:44.285Z (about 2 months ago)
• Topics: coding-katas, dart, kata, katas, tdd
• Language: Dart
• Homepage:
• Size: 8.14 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Solving coding katas in Dart language using TDD   

### Coverage

**Use**: `dart run test --coverage=./coverage && dart pub global run coverage:format_coverage --packages=.dart_tool/package_config.json --report-on=lib --lcov -o ./coverage/lcov.info -i ./coverage`

# Arlo's Commit Notation Cheat Sheet

## Risk Categories

| Symbol | Risk Description                     |

|--------|--------------------------------------|

| .      | Provable (changes are easy to verify)|

| -      | Tested (changes have been tested)    |

| !      | Single Action (single, atomic change)|

| @      | Other (miscellaneous changes)        |

## Action Categories

| Symbol | Action Description                       |

|--------|------------------------------------------|

| r      | Refactoring (improving code structure)   |

| e      | Environment (non-code changes)           |

| d      | Documentation (changes to documentation) |

| t      | Test only (changes to tests)             |

| F      | Feature (new features)                   |

| B      | Bugfix (fixing bugs)                     |

## Examples

- `.r rename variable`: Provable refactoring change, such as renaming a variable.

- `-e update build script`: Tested change to the environment, such as updating a build script.

- `!B fixed spelling on label`: Single action bugfix, like fixing a spelling error on a label.

- `@d update README`: Miscellaneous documentation change, like updating the README file.

## Commit Message Guidelines

- Always use the appropriate risk and action symbols to describe the change.

- Provide a concise description of the change after the symbols.

## Example Commit Messages

- `.r rename variable`: This commit renames a variable, which is a provable refactoring change.

- `-e update build script`: This commit updates a build script, indicating a tested environment change.

- `!B fixed spelling on label`: This commit fixes a spelling error on a label, a single action bugfix.

- `@d update README`: This commit updates the README file, categorized as other documentation change.

By using this notation, you can clearly and concisely describe the nature and risk of your changes in commit messages.