-
-
Notifications
You must be signed in to change notification settings - Fork 689
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving instructions from dnd character exercise #2603
Improving instructions from dnd character exercise #2603
Conversation
I guess that for this pr to be applied I should also modify this |
The documentation for practice exercises is generally generated from the problem specifications - in fact from the document you linked to above. This means that any changes made to a practice exercise's $ bin/fetch-configlet
Fetching configlet...
Downloaded configlet 4.0.0-beta.16 to ./bin/configlet
$ bin/configlet sync --docs --exercise dnd-character --update
Updating cached 'problem-specifications' data...
Checking exercises...
[warn] docs: instructions unsynced: dnd-character
sync the above docs ([y]es/[n]o)? y
Updated the docs for 1 Practice Exercise
The `dnd-character` exercise has up-to-date docs! Since the problem specifications are used by all Exercism tracks, the instructions there are written so that they can apply to each track. This means that they explicitly do not contain any implementation details for an exercise, just a description of the problem to solve. Any track-specific information that we as maintainers think are valid to append to the instructions can be placed in the exercise's Finally, exercises can optionally also contain a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the above in mind, I would propose the following:
- The
.docs/instructions.md
should never deviate from the problem specifications, so please roll back any changes to it - Add additional instructions that are relevant for the Java track in the
.docs/instructions.append.md
. - Don't add
.docs/introduction.md
as there is no introduction needed before the instructions from the problem specifications.
…rifications into instructions.append
Thanks for the review Sander, I made the changes you asked. |
Just FYI: I haven't forgotten about this PR, I just haven't had time to write down my thoughts on it. I'll try to have it reviewed some time this week! |
No problem! and thanks for letting me know! |
# Instructions append | ||
|
||
~~~~exercism/note | ||
Remember that you character should be ``unique``. If you are not sure how to achieve it review [Constructors][constructors] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean by this? I'm not familiar with any unique
concept in Java.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to refer to this test
public void testUniqueCharacterIsCreated() { |
If I look at the original issue I'm not sure that these additions really improve the instructions. I see two ways of going forward:
I personally favor the second option. |
Yeah you're right, the changes are minimum and the second options tends to be the way of solve exercises in exercism, so what do we do with the issue? we close it? |
Yes I think we should explain our perspective and close it. |
pull request
the issue addresses: #2334
The goal is to improve the documentation on dnd character exercise.
Reviewer Resources:
Track Policies