The default implementation works as follows:
- The
representation.txt
contains the concatenated solution files- Solution files are separated by an empty line
- Solution files are identified via the the
.files.solution[]
property in the.meta/config.json
file
- The
mapping.json
contains an empty JSON object ({}
)
- Blank files in the solution files are removed in the
representation.txt
- Line-based trailing whitespace in the solution files is removed in the
representation.txt
The Docker image to automatically create a representation for Raku solutions submitted to Exercism.
To create a representation for an arbitrary exercise, do the following:
- Open a terminal in the project's root
- Run
./bin/run.sh <exercise-slug> <solution-dir> <output-dir>
Once the representer has finished, its results will be written to <output-dir>/representation.txt
and <output-dir>/mapping.json
.
This script is provided for testing purposes, as it mimics how representers run in Exercism's production environment.
To create a representation for an using the Docker image, do the following:
- Open a terminal in the project's root
- Run
./bin/run-in-docker.sh <exercise-slug> <solution-dir> <output-dir>
Once the representer has finished, its results will be written to <output-dir>/representation.txt
and <output-dir>/mapping.json
.
To run the tests to verify the behavior of the representer, do the following:
- Open a terminal in the project's root
- Run
./bin/run-tests.sh
These are golden tests that compare the representation.txt
and mapping.json
generated by running the current state of the code against the "known good" tests/<test-name>/representation.txt
and tests/<test-name>/mapping.json
. All files created during the test run itself are discarded.
When you've made modifications to the code that will result in a new "golden" state, you'll need to generate and commit a new tests/<test-name>/representation.txt
and tests/<test-name>/mapping.json
file.
This script is provided for testing purposes, as it mimics how representers run in Exercism's production environment.
To run the tests to verify the behavior of the representer using the Docker image, do the following:
- Open a terminal in the project's root
- Run
./bin/run-tests-in-docker.sh
These are golden tests that compare the representation.txt
and mapping.json
generated by running the current state of the code against the "known good" tests/<test-name>/representation.txt
and tests/<test-name>/mapping.json
. All files created during the test run itself are discarded.
When you've made modifications to the code that will result in a new "golden" state, you'll need to generate and commit a new tests/<test-name>/representation.txt
and tests/<test-name>/mapping.json
file.