🤖 Sync exercise files keys based on file path patterns #107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To help tracks define the files in the exercise's
.meta/config.json
file, we've added support for defining these file patterns in the track'sconfig.json
file. See this PR.This PR updates the file paths defined in the
files
property of each exercise's.meta/config.json
file according to the file patterns defined in the track'sconfig.json
file.We only update a file path in the
.meta/config.json
file if:config.json
file.meta/config.json
fileThis means that exercises that had already defined files in the
.meta/config.json
won't be touched in this PR.Note that this PR is just an easy way for tracks to populate the files in the
.meta/config.json
files. Tracks are completely free to add/change/remove the files in their.meta/config.json
files.In the future, we'll update
configlet
to include this functionality. If you'd like me to re-run the script because changes have been made, feel free to ping me on Slack (@ErikSchierboom).Tracking
exercism/v3-launch#20