Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions exercises/practice/calculator-conundrum/.meta/design.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Design

## Analyzer

This exercise could benefit from the following rules in the [analyzer]:

- `essential`: Verify that the solution is not wrapping all the code in a try catch statement
- `actionable`: If the solution uses an `if` statement, instruct the student to use the `switch case` statement instead.
- `informative`: If the solution does not use `HashMap`, instruct the student to use the operator as a key and a BiFunction implementing the calculation
Explain that it is more efficient for performance, and it removes the cyclomatic complexity
- `informative`: If the solution does not throw the exception for `Operation cannot be null` and `Operation cannot be empty` at the beginning, instruct the student to do so
Explain that it is better to fail fast, and it will make the code less error-prone and more readable

[analyzer]: https://github.com/exercism/java-analyzer