You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exercises/concept/calculator-conundrum/.meta/design.md
+13Lines changed: 13 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,3 +18,16 @@
18
18
19
19
-`conditionals-if`: know how to do conditional logic.
20
20
-`switch-statement`: know how to work with a `switch` statement.
21
+
22
+
## Analyzer
23
+
24
+
This exercise could benefit from the following rules in the [analyzer]:
25
+
26
+
-`essential`: Verify that the solution is not wrapping all the code in a try catch statement
27
+
-`actionable`: If the solution uses an `if` statement, instruct the student to use the `switch case` statement instead.
28
+
-`informative`: If the solution does not use `HashMap`, instruct the student to use the operator as a key and a BiFunction implementing the calculation
29
+
Explain that it is more efficient for performance, and it removes the cyclomatic complexity
30
+
-`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
31
+
Explain that it is better to fail fast, and it will make the code less error-prone and more readable
0 commit comments