|
|
@@ -30,7 +30,7 @@ Our policies are not set-in-stone. They represent directions chosen at a point i
|
|
30
|
30
|
|
|
31
|
31
|
> Most (all?) exercises should be implemented in the form of instance methods since they contain "domain logic" and we (Exercism) want to encourage exemplary software.
|
|
32
|
32
|
|
|
33
|
|
-References: [[1](https://github.com/exercism/xjava/issues/177#issuecomment-261291741)]
|
|
|
33
|
+References: [[1](https://github.com/exercism/java/issues/177#issuecomment-261291741)]
|
|
34
|
34
|
|
|
35
|
35
|
### Starter implementations
|
|
36
|
36
|
|
|
|
@@ -40,7 +40,7 @@ References: [[1](https://github.com/exercism/xjava/issues/177#issuecomment-26129
|
|
40
|
40
|
`throw new UnsupportedOperationException("Delete this statement and provide your own implementation.");`
|
|
41
|
41
|
> - Exercises 21+: provide no stubs, but mention any "interesting" interface aspects in the HINT.md file (which gets merged into the README.md for the exercise).
|
|
42
|
42
|
|
|
43
|
|
-References: [[1](https://github.com/exercism/xjava/issues/178)]
|
|
|
43
|
+References: [[1](https://github.com/exercism/java/issues/178)]
|
|
44
|
44
|
|
|
45
|
45
|
### Do not make user-facing classes `final`
|
|
46
|
46
|
|
|
|
@@ -50,22 +50,22 @@ References: [[1](https://github.com/exercism/xjava/issues/178)]
|
|
50
|
50
|
|
|
51
|
51
|
> All but the first test in an exercise test suite should be annotated `@Ignore("Remove to run test")` (single test) or `@Ignore("Remove to run tests")` (parametrized test).
|
|
52
|
52
|
|
|
53
|
|
-References: [[1](https://github.com/exercism/xjava/issues/101#issuecomment-249349204)]
|
|
|
53
|
+References: [[1](https://github.com/exercism/java/issues/101#issuecomment-249349204)]
|
|
54
|
54
|
|
|
55
|
55
|
### Multiple file submissions
|
|
56
|
56
|
|
|
57
|
57
|
> The first exercise in the track whose test suite mandates multiple solution files should be accompanied by a HINT.md file reminding the practitioner that the CLI supports multiple file submissions.
|
|
58
|
58
|
|
|
59
|
|
-References: [[1](https://github.com/exercism/xjava/issues/365#issuecomment-292533120)]
|
|
|
59
|
+References: [[1](https://github.com/exercism/java/issues/365#issuecomment-292533120)]
|
|
60
|
60
|
|
|
61
|
61
|
### Good first patches
|
|
62
|
62
|
|
|
63
|
|
-> Aim to keep 10-20 small and straightforward issues open at eny given time. Identify any such issues by applying the "Good first patch" label. You can view the current list of these issues [here](https://github.com/exercism/xjava/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+patch%22).
|
|
|
63
|
+> Aim to keep 10-20 small and straightforward issues open at eny given time. Identify any such issues by applying the "Good first patch" label. You can view the current list of these issues [here](https://github.com/exercism/java/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+patch%22).
|
|
64
|
64
|
|
|
65
|
|
-References: [[1](https://github.com/exercism/xjava/issues/220#issue-196447088)]
|
|
|
65
|
+References: [[1](https://github.com/exercism/java/issues/220#issue-196447088)]
|
|
66
|
66
|
|
|
67
|
67
|
### Simple onboarding
|
|
68
|
68
|
|
|
69
|
69
|
> The Installing Java instructions should seek to minimize the number of steps and the number of concepts a new-to-the-track practitioner needs to learn to get to coding.
|
|
70
|
70
|
|
|
71
|
|
-References: [[1](https://github.com/exercism/xjava/issues/395#issue-215734887)]
|
|
|
71
|
+References: [[1](https://github.com/exercism/java/issues/395#issue-215734887)]
|