-
-
Notifications
You must be signed in to change notification settings - Fork 45
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
exercises/practice/anagram: add an append with instructions about the order of the return values #328
Conversation
… order of the return values
Clarify what this track expects. Context: https://forum.exercism.org/t/14816/ |
+cc @exercism/cross-track-maintainers |
Is there a particular reason we need the rest of the append? That seems like content better covered elsewhere in the track docs. |
No clue :) I just tidied up the formatting slightly. I can revert the changes to the other lines if you prefer. |
There appear to be no scheme maintainers (https://github.com/orgs/exercism/teams/scheme) so let's just clean it up. It does echo the https://exercism.org/docs/tracks/scheme/tests page. |
https://github.com/search?q=repo%3Aexercism%2Fscheme+%22Running+and+testing+your+solutions%22&type=code shows that this is a common append. The Scheme track generates their test-specific documentation programatically like https://github.com/exercism/scheme/blob/566dfd3696fd94d4066d610d4a8d8928983d7048/input/docs/TESTS.ss but I think the appends are by hand. So we could edit those without an issue. I suspect the append is primarily for folks working offline, but they can refer to the track-specific docs about testing instead. I think it'll be simpler to address these appends in a later PR and just merge this PR for now. |
Offline people get the test instructions in HELP.md. The "how to test" text gets added into it. |
Happy to drop that append stuff ... but maybe that should be a separate (follow up) PR? This batch of PRs is specific to discussing the order of the elements. |
That’s what i’m thinking as well. I’ll merge this in though. |
Please see #329 |
No description provided.