Allow specifying the track repository directory #50
Assignees
Labels
kind: feature
User-facing enhancement
Comments
ee7
added a commit
to ee7/exercism-configlet
that referenced
this issue
Oct 23, 2020
With this commit, we can now establish a beginning state by specifying:
- a track directory
- a problem-specifications directory
- the offline mode
This allows us to do black-box testing of the release binary, running
something like:
canonical_data_syncer -t /tmp/python -p /tmp/my_prob_specs --offline
and then asserting that the changes made are as expected.
Closes: exercism#50
ee7
added a commit
to ee7/exercism-configlet
that referenced
this issue
Oct 23, 2020
With this commit, we can now establish a beginning state by specifying:
- a track directory
- a problem-specifications directory
- the offline mode
This allows us to do black-box testing of the release binary, running
something like:
canonical_data_syncer -t /tmp/python -p /tmp/my_prob_specs --offline
and then asserting that the changes made are as expected.
Closes: exercism#50
ee7
added a commit
to ee7/exercism-configlet
that referenced
this issue
Oct 30, 2020
With this commit, we can now establish a beginning state by specifying:
- a track directory
- a problem-specifications directory
- the offline mode
This allows us to do black-box testing of the release binary, running
something like:
canonical_data_syncer -t /tmp/python -p /tmp/my_prob_specs --offline
and then asserting that the changes made are as expected.
Closes: exercism#50
ee7
added a commit
to ee7/exercism-configlet
that referenced
this issue
Jan 26, 2021
With this commit, we can now establish a beginning state by specifying:
- a track directory
- a problem-specifications directory
- the offline mode
This allows us to do black-box testing of the release binary, running
something like:
configlet -t /tmp/python -p /tmp/my_prob_specs --offline
and then asserting that the changes made are as expected.
Closes: exercism#50
ee7
added a commit
to ee7/exercism-configlet
that referenced
this issue
Jan 26, 2021
With this commit, we can now establish a beginning state by specifying:
- a track directory
- a problem-specifications directory
- the offline mode
This allows us to do black-box testing of the release binary, running
something like:
configlet -t /tmp/python -p /tmp/my_prob_specs --offline
and then asserting that the changes made are as expected.
Closes: exercism#50
ee7
added a commit
that referenced
this issue
Jan 26, 2021
This commit allows the configlet binary to act on a different directory
than its own. This is useful in general, but it will also help us to
test configlet itself - we can now establish an initial state for
end-to-end tests by specifying:
- a track directory
- a problem-specifications directory
- the offline mode
That allows us to do black-box testing of the release binary, running
something like:
configlet sync -t=/tmp/python -p=/tmp/my_prob_specs -o -m=include
and then asserting that the changes made are as expected.
Note that we implement `-t, --track-dir` as a global option, rather than
an option for `sync` - it will also be useful for e.g. `lint`.
Some decisions:
- Set the default value of `conf.trackDir` explicitly to the current
directory in `cli.nim`.
- Determine the `tests.toml` path from `conf.trackDir`, but don't change
the current directory to `conf.trackDir`.
Closes: #50
ee7
added a commit
to ee7/exercism-configlet
that referenced
this issue
Jan 27, 2021
This commit allows the configlet binary to act on a different directory
than its own. This is useful in general, but it will also help us to
test configlet itself - we can now establish an initial state for
end-to-end tests by specifying:
- a track directory
- a problem-specifications directory
- the offline mode
That allows us to do black-box testing of the release binary, running
something like:
configlet sync -t=/tmp/python -p=/tmp/my_prob_specs -o -m=include
and then asserting that the changes made are as expected.
Note that we implement `-t, --track-dir` as a global option, rather than
an option for `sync` - it will also be useful for e.g. `lint`.
Some decisions:
- Set the default value of `conf.trackDir` explicitly to the current
directory in `cli.nim`.
- Determine the `tests.toml` path from `conf.trackDir`, but don't change
the current directory to `conf.trackDir`.
Closes: exercism#50
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should allow the user to specify the directory of the track to work with. It should default to the current directory if not specified. I'm thinking it should just be the last, non-named parameter.
The
configlettool for Exercism v2 has a similar feature BTW.The text was updated successfully, but these errors were encountered: