A Practice Exercise on an Exercism track is often implemented from a specification in the exercism/problem-specifications repo.
Exercism deliberately requires that every exercise has its own copy of certain files (like .docs/instructions.md), even when that exercise exists in problem-specifications.
Therefore configlet has a sync command, which can check that such Practice Exercises on a track are in sync with that upstream source, and can update them when updates are available.
There are three kinds of data that can be updated from problem-specifications: documentation, metadata, and tests.
There is also one kind of data that can be populated from the track-level config.json file: filepaths in exercise config files.
We describe the checking and updating of these data kinds in individual sections below, but as a quick summary:
configlet sync only operates on exercises that exist in the track-level config.json file.
Therefore if you are implementing a new exercise on a track and want to add the initial files with configlet sync, please add the exercise to the track-level config.json file first.
If the exercise is not yet ready to be user-facing, please set its status value to wip.configlet sync makes no changes to the track, and checks every data kind for every exercise.--docs, --filepaths, --metadata, and --tests options.--update option.--update --yes.--update --tests include --exercise prime-factors.problem-specifications repo, add --offline --prob-specs-dir /path/to/local/problem-specifications
configlet sync tries to maintain the key order in exercise .meta/config.json files when updating.
To write these files in a canonical form without syncing, please use the configlet fmt command.
However, configlet sync does add (possibly empty) required keys (authors, files, blurb) when they are missing.
This is less "sync-like", but more ergonomic: when implementing a new exercise, you can use sync to create a starter .meta/config.json file.configlet sync removes keys that are not in the spec.
Custom key/value pairs are still supported: they must be written inside a JSON object named custom.Note that in configlet releases 4.0.0-alpha.34 and earlier, the sync command operated only on tests.
The sync command can be used check or update Practice Exercise docs, metadata, and tests from 'problem-specifications'.
It can also check or populate missing files values for Concept/Practice Exercises from the track 'config.json'.
configlet [global-options] sync [command-options]
Global options:
-h, --help Show this help message and exit
--version Show this tool's version information and exit
-t, --track-dir <dir> Specify a track directory to use instead of the current directory
-v, --verbosity <verbosity> The verbosity of output. Allowed values: q[uiet], n[ormal], d[etailed]
Options for sync:
-e, --exercise <slug> Only operate on this exercise
-p, --prob-specs-dir <dir> Use this 'problem-specifications' directory, rather than cloning temporarily
-o, --offline Do not check that the directory specified by --prob-specs-dir is up to date
-u, --update Prompt to update the seen data that are unsynced
-y, --yes Auto-confirm prompts from --update for updating docs, filepaths, and metadata
--docs Sync Practice Exercise '.docs/introduction.md' and '.docs/instructions.md' files
--filepaths Populate empty 'files' values in Concept/Practice exercise '.meta/config.json' files
--metadata Sync Practice Exercise '.meta/config.json' metadata values
--tests [mode] Sync Practice Exercise '.meta/tests.toml' files.
The mode value specifies how missing tests are handled when using --update.
Allowed values: c[hoose], i[nclude], e[xclude] (default: choose)
A Practice Exercise that is derived from the problem-specifications repo must have a .docs/instructions.md file (and possibly a .docs/introduction.md file too) containing the exercise documentation from problem-specifications.
To check every Practice Exercise on the track for available documentation updates (exiting with a non-zero exit code if at least one update is available):
configlet sync --docs
To interactively update the docs for every Practice Exercise, add the --update option (or -u for short):
configlet sync --docs --update
To non-interactively update the docs for every Practice Exercise, add the --yes option (or -y for short):
configlet sync --docs --update --yes
To operate on a single Practice Exercise, use the --exercise option (or -e for short).
For example, to non-interactively update the docs for the prime-factors exercise:
configlet sync --docs -uy -e prime-factors
Every exercise on a track must have a .meta/config.json file.
For a Practice Exercise that is derived from the problem-specifications repo, this file should contain the blurb, source and source_url key/value pairs that exist in the corresponding upstream metadata.toml file.
To check every Practice Exercise for available metadata updates (exiting with a non-zero exit code if at least one update is available):
configlet sync --metadata
To interactively update the metadata for every Practice Exercise, add the --update option (or -u for short):
configlet sync --metadata --update
To non-interactively update the metadata for every Practice Exercise, add the --yes option (or -y for short):
configlet sync --metadata --update --yes
To operate on a single Practice Exercise, use the --exercise option (or -e for short).
For example, to non-interactively update the metadata for the prime-factors exercise:
configlet sync --metadata -uy -e prime-factors
If a track implements an exercise for which test data exists in the problem-specifications repo, the exercise must contain a .meta/tests.toml file.
The goal of the tests.toml file is to keep track of which tests are implemented by the exercise.
Tests in this file are identified by their UUID and each test has a boolean value that indicates if it is implemented by that exercise.
A tests.toml file has this format:
# This is an auto-generated file.
#
# Regenerating this file via `configlet sync` will:
# - Recreate every `description` key/value pair
# - Recreate every `reimplements` key/value pair, where they exist in problem-specifications
# - Remove any `include = true` key/value pair (an omitted `include` key implies inclusion)
# - Preserve any other key/value pair
#
# As user-added comments (using the # character) will be removed when this file
# is regenerated, comments can be added via a `comment` key.
[1e22cceb-c5e4-4562-9afe-aef07ad1eaf4]
description = "basic"
[79ae3889-a5c0-4b01-baf0-232d31180c08]
description = "lowercase words"
[ec7000a7-3931-4a17-890e-33ca2073a548]
description = "invalid input"
include = false
comment = "excluded because we don't want to add error handling to the exercise"
In this case, the track has chosen to implement two of the three available tests.
If a track uses a test generator to generate an exercise's test suite, it must use the contents of the tests.toml file to determine which tests to include in the generated test suite.
To check every Practice Exercise tests.toml file for available tests updates (exiting with a non-zero exit code if there is at least one test case that appears in the exercise's canonical data, but not in the tests.toml):
configlet sync --tests
To interactively update the tests.toml file for every Practice Exercise, add the --update option:
configlet sync --tests --update
For each missing test, this prompts the user to choose whether to include/exclude/skip it, and updates the corresponding tests.toml file accordingly.
Configlet writes an exercise's tests.toml file when the user has finished making choices for that exercise.
This means that you can terminate configlet at a prompt (for example, by pressing Ctrl-C in the terminal) and only lose the syncing decisions for at most one exercise.
To non-interactively include every unseen test case, use --tests include.
For example, to do so for an exercise named prime-factors:
configlet sync --tests include -u -e prime-factors
Remember to actually implement these tests on the track!
Finally, the sync command also handles "syncing" from a source that isn't problem-specifications - the track-level config.json file.
Every Concept Exercise and Practice Exercise must have a .meta/config.json file with a files object that specifies the (relative) locations of the files that the exercise uses.
Such filepaths usually follow a simple pattern, and so configlet can populate the exercise-level values from patterns in the files key of the track-level config.json file.
To check that every Concept Exercise and Practice Exercise on the track has a fully populated files key (or at least one that cannot be populated from the track-level files key):
configlet sync --filepaths
(Note that configlet lint will also produce an error when an exercise has a missing/empty files key.)
To populate empty/missing values of the exercise-level files key for every Concept Exercise and Practice Exercise from the patterns in the track-level files key:
configlet sync --filepaths --update
To do this non-interactively and for a single exercise named prime-factors:
configlet sync --filepaths -uy -e prime-factors
sync when adding a new exercise to a trackThe sync command is useful when adding a new exercise to a track.
If you are adding a Practice Exercise named foo that exists in problem-specifications, one possible workflow is:
config.json file for the exercise foo.
This makes the exercise visible to configlet sync.configlet sync --docs --filepaths --metadata -uy -e foo to create the exercise's documentation, and a starter .meta/config.json file with populated files, blurb, and perhaps source and source_url values..meta/config.json file as desired.
For example, add yourself to the authors array.configlet sync --tests include -u -e foo to create a .meta/tests.toml file with every test included..meta/tests.toml file, and add include = false to any test case that the exercise will not implement..meta/tests.toml.