mirror of
https://github.com/correl/elm.git
synced 2024-11-29 03:00:10 +00:00
73 lines
2 KiB
Markdown
73 lines
2 KiB
Markdown
|
# Grade School
|
||
|
|
|
||
|
|
Given students' names along with the grade that they are in, create a roster
|
||
|
|
for the school.
|
||
|
|
|
||
|
|
In the end, you should be able to:
|
||
|
|
|
||
|
|
- Add a student's name to the roster for a grade
|
||
|
|
- "Add Jim to grade 2."
|
||
|
|
- "OK."
|
||
|
|
- Get a list of all students enrolled in a grade
|
||
|
|
- "Which students are in grade 2?"
|
||
|
|
- "We've only got Jim just now."
|
||
|
|
- Get a sorted list of all students in all grades. Grades should sort
|
||
|
|
as 1, 2, 3, etc., and students within a grade should be sorted
|
||
|
|
alphabetically by name.
|
||
|
|
- "Who all is enrolled in school right now?"
|
||
|
|
- "Grade 1: Anna, Barb, and Charlie. Grade 2: Alex, Peter, and Zoe.
|
||
|
|
Grade 3…"
|
||
|
|
|
||
|
|
Note that all our students only have one name. (It's a small town, what
|
||
|
|
do you want?)
|
||
|
|
|
||
|
|
|
||
|
|
## For bonus points
|
||
|
|
|
||
|
|
Did you get the tests passing and the code clean? If you want to, these
|
||
|
|
are some additional things you could try:
|
||
|
|
|
||
|
|
- If you're working in a language with mutable data structures and your
|
||
|
|
implementation allows outside code to mutate the school's internal DB
|
||
|
|
directly, see if you can prevent this. Feel free to introduce additional
|
||
|
|
tests.
|
||
|
|
|
||
|
|
Then please share your thoughts in a comment on the submission. Did this
|
||
|
|
experiment make the code better? Worse? Did you learn anything from it?
|
||
|
|
|
||
|
|
## Elm Installation
|
||
|
|
|
||
|
|
Refer to the [Exercism help page](http://exercism.io/languages/elm) for Elm
|
||
|
|
installation and learning resources.
|
||
|
|
|
||
|
|
## Writing the Code
|
||
|
|
|
||
|
|
The first time you start an exercise, you'll need to ensure you have the
|
||
|
|
appropriate dependencies installed.
|
||
|
|
|
||
|
|
```bash
|
||
|
|
$ npm install
|
||
|
|
```
|
||
|
|
|
||
|
|
Execute the tests with:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
$ npm test
|
||
|
|
```
|
||
|
|
|
||
|
|
Automatically run tests again when you save changes:
|
||
|
|
|
||
|
|
```bash
|
||
|
|
$ npm run watch
|
||
|
|
```
|
||
|
|
|
||
|
|
As you work your way through the test suite, be sure to remove the `skip <|`
|
||
|
|
calls from each test until you get them all passing!
|
||
|
|
|
||
|
|
## Source
|
||
|
|
|
||
|
|
A pairing session with Phil Battos at gSchool [http://gschool.it](http://gschool.it)
|
||
|
|
|
||
|
|
## Submitting Incomplete Solutions
|
||
|
|
It's possible to submit an incomplete solution so you can see how others have completed the exercise.
|