hello-world: Change to always expect "Hello, World!"#544
hello-world: Change to always expect "Hello, World!"#544rbasso merged 1 commit intoexercism:masterfrom rbasso:hello-world-simplified
Conversation
| { | ||
| "hello":{ | ||
| "description":"Say Hi!", | ||
| "expected":"Hello, World!" |
There was a problem hiding this comment.
There is no standard format for the canonical-data.json, so I used the one I proposed here. If by any chance it gets accepted without change, it will be one less file to update. 😄
There was a problem hiding this comment.
Thanks for taking over. It's a big effort, given that it affects new user experience for any languages that have it. Thus, all help is appreciated (I'm relieved and grateful!). You know you have my support.
A few comments.
It's tough for me to put myself in a new user's shoes anymore, since it has been too long since I was one.
| @@ -1,4 +1,4 @@ | |||
| --- | |||
| blurb: 'Greet the user by name, or by saying "Hello, World!" if no name is given.' | |||
| blurb: 'Just say "Hello, World!"' | |||
There was a problem hiding this comment.
Given that this exercise gets shown in e.g. http://exercism.io/languages/c/exercises , it may be nice to display prominently in this line that this is an introductory exercise.
There was a problem hiding this comment.
I changed it, but I really don't know what would be good to put there.
If you have any suggestion, please write it here and I'll change it immediately.
|
|
||
| If a name is not given, the response should be "Hello, World!" | ||
|
|
||
| ## Test-Driven Development |
There was a problem hiding this comment.
Hmm. The fact that this was here makes me wonder whether it should be put into a second introductory exercise, whatever exercise is used as intro-to-TDD. Unless we think each track should deal with this.
Or, maybe we keep it here, but note that in this exercise the test suite is a single case, and in later ones it will have more cases.
There was a problem hiding this comment.
I think that the instructions where misplaced.
Not all exercises implemented the hello-world exercise. Moving the instructions to leap's description.md would just reproduce the problem in another place.
The immediate solution I can think of is track-dependent: Move it to the HINTS.md from the first exercise that is not hello-world. This is more flexible than forcing it to be leap.
This way, each track can customize the instructions to reflect what are the best practices for testing in the language. Not all languages are so TDD focused as ruby seems to be, specially the strongly-typed ones, that force users to type-check everything before running a single test.
I just create a Gist of a HINTS.md file with the old instructions here, to make migration easier. If you think this is a good idea, we could link it in a more visible place to help the track maintainers.
There was a problem hiding this comment.
I agree that the instrutions were misplaced. Languages can use the proposed hint for their next exercise, whatever it may be.
| readable as we can. However, solutions to the hello-world exercise will not be | ||
| reviewed by a person, but by rikki- the robot, who will offer an encouraging | ||
| word. | ||
| If everything goes well, you will be ready to fetch your first real exercise. |
There was a problem hiding this comment.
Very nice. One note (probably to myself): while the instructions we lose in this Pull seem appropriate to remove here, they might be useful somewhere else. If we do end up choosing a intro-to-tdd exercise, this might be a good source for that description.md.
|
|
||
| exercism skip $TRACK_ID hello-world | ||
| - Write a function that says "Hello, World!". | ||
| - Run the tests and make sure that they succeed. |
There was a problem hiding this comment.
Maybe "Run the tests" should be "Run the test(s)", as I expect most languages to only have a single test.
There was a problem hiding this comment.
Run the test file? This is always the case, unless there are tracks with multiple files for testing?
There was a problem hiding this comment.
"Run the test suite..." ?
There was a problem hiding this comment.
Run the test suite is a very nice suggestion! I like that.
|
The time for merging has come (in fact we are 4 hours and 30 minutes late), so I'm merging this as promised/agreed and hope that all the tracks also merge their changes soon, to keep consistency
|
* hello-world: Change to always expect "Hello, World!" see exercism/problem-specifications#544 * hello-world: add stub file
by always expecting "Hello, World!" Change in x-common: [here](exercism/problem-specifications#544) Upcoming new exercise to kinda replace `hello-world`: [here](exercism/problem-specifications#759) Since this `hello-world` is just meant to be a sanity check for everything working, I also went ahead and removed the use of class for the sake of simplicity. We can introduce classes with the next `two-fer` exercise.
by always expecting "Hello, World!" Change in x-common: [here](exercism/problem-specifications#544) Upcoming new exercise to kinda replace `hello-world`: [here](exercism/problem-specifications#759) Since this `hello-world` is just meant to be a sanity check for everything working, I also went ahead and removed the use of class for the sake of simplicity. We can introduce classes with the next `two-fer` exercise.
As discussed in #520, the exercise
hello-worldis too complex to fulfill its purpose and we decided to simplify it.The new test suite will simply expect the string "Hello, World!", and will serve mainly as a sanity check that everything is working.
This change may disrupt some tracks that already have it implemented, so we are scheduling the merging of this PR to allow the @exercism/track-maintainers to sync track-specific changes with
x-common.The merging is tentatively scheduled to: 2016-02-20 00:01 UTC +-1 day 😄
Please direct any question/critic to #520, so that we can keep the discussion focused there.
Closes #520.