The first core exercise on the track should be auto-approved.
This means that mentor approval isn't needed in order to move
forward when the exercise has been completed.
Currently any hello-world exercises are auto-approved in the
backend of v2 but this special handling might be removed later
which is why this also needs to be set in config.json.
This runs the configlet fmt command, which normalizes the
contents and ordering of keys in the track config and
maintainers config.
This will let us script changes to the config files without
having unnecessary noise in the diffs when submitting pull
requests.
* Update version file v2.2.0 --> v2.3.0
* Add new test for list of nested list.
* Add updated test
* Make changes to code and make it more readable
* Fix data set and indentation
* Fix indentation error
* Fix Bug
go-counting: use provided enumeration instead of Strings (#1461)
* go-counting: use provided enumeration instead of Strings
Use of enumeration should be consistent across the test suite.
* update example solution to match new test expectations
* fix return type
Poker: Update test to exactly match the canonical data and add version file (#1432)
* Poker: Update test to exactly match the canonical data and add version file
* Change PokerTest.java,Card.java and Hand.java in order to match with canonical data and add version file.
* Correct Card.java in order to match with canonical data.
* Change indentation and correct mistakes
* Add import to PokerTest
* Fix indentation and correct mistakes
* Change variable's name from snake case to camel case
* Fix variable's name
Add some more best practices that I've seen come up on reviews quite often.
Add a section on not returning null since the canonical data often cause
confusion about this.
Add a section on using ExpectedException since this was something we agreed
a while ago but it's not documented anywhere.
We have decided that every exercise with diffulty less than 3 should
reference the hello world tutorial to make it easier for people to solve
those exercises. This has now been added to our policies doc.
We also now reference those policies in the contributing doc in the section
for adding new exercises.