-
-
Notifications
You must be signed in to change notification settings - Fork 546
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
Implement canonical data for all non-deprecated exercises #552
Comments
Should canonical data be required for any new exercises added (if it isn't already)? |
That's a good question. I think that it should be encouraged, but another option is to open a "canonical data" issue for the new exercise and let someone else tackle it. |
Given a "Proof of Concept" as the given example program and tests, the canonical is probably not a leap for a second party to tackle, and, presumably, the creator is interested and so still available for input. I think that works. |
Don't mind me, just putting this somewhere where I can find it easily again: curl http://x.exercism.io/v3/problems/data-todos | jq '.[] | map(select(.["slug"] == "accumulate"))' Note that the contribute page 1: Link updated to show, as it has moved since this was posted. |
Hi. I'm going to mark all the subtasks of this task as good first patch. |
Both links mentioned in the description are dead now: I assume the valid one should be Getting Involved in an Exercism Language Track to avoid any confusion for newcomers. @kytrinyx, could you please update the description, here is the link: |
Good call, @m-a-ge, I've rewritten a bit to add the suggested link, and fix the two dead ones. |
Update documentation about generated test cases
I've just ran a command (
|
A number of the exercises are still missing canonical data. Adding this would help make it easier for people to get involved in contributing to Exercism language tracks.
Canonical data is a standardized set of test inputs/outputs that makes it easier to implement exercises from specifications and keep exercises consistent as the test suites evolve.
These issues link back to this one. Once they're all fixed and closed, this issue can also be closed.
The text was updated successfully, but these errors were encountered: