problem-specifications
problem-specifications copied to clipboard
exercism
Shared metadata for exercism exercises.
I noticed while reviewing a PR for this exercise to the bash track that there are some errors (I am a music composition major). I believe that as a learning...
In the canonical data for the "say" problem: https://github.com/exercism/x-common/blob/master/exercises/say/canonical-data.json * The descriptions should be descriptive. In most cases the description is the same as the output. ``` { "description": "zero",...
The specification for the [Robot Names exercise](https://github.com/exercism/problem-specifications/blob/main/exercises/robot-name/description.md) says the solution "must ensure that every *existing* robot has a *unique* name" (confusing words emphasized). The use of "existing" together with "unique"...
I've encountered solution where the student only checked if the sides are 0 and not if they are negative. In other cases only one of the functions was checking if...
exercises/rna-transcription/description.md Instructions and test could be improved for this exercise, and possibly a review of the instructions and tests for the same exercise where it exists on other tracks.- but...
Would it be helpful at the problem-specification level to logically group exercises? I am thinking this may be valuable in auto-configuring some tracks or at least providing some meta-organization. Some...
> What is a valid input? 20 s? 3:20 pm? half past noon? > Once we have the input, we need to be able to "add and subtract minutes to...
There is a json schema definition for the `canoncial-data.json` file. https://github.com/exercism/problem-specifications/blob/master/canonical-schema.json However this still allows for arbitrary keys containing spaces. These keys are often used for specifying test input arguments....
Hi. First time here. Should the **Rational Numbers** test suite check that an exception is raised for division by zero? Normally, I would say that it is a detail that...
I think the VLQ specification should be more explicit about building 7-bit bytes starting from the right (least significant bits): Correct order: start from the right (least significant bits): 32...
