Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add file patterns to config.json #19

Closed
ErikSchierboom opened this issue Feb 17, 2021 · 1 comment
Closed

Add file patterns to config.json #19

ErikSchierboom opened this issue Feb 17, 2021 · 1 comment

Comments

@ErikSchierboom
Copy link
Member

ErikSchierboom commented Feb 17, 2021

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's config.json file. See this PR.

We'll send PRs to update 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's config.json file.

We only update a file path in the .meta/config.json file if:

  • The file path pattern is a non-empty array in the config.json file
  • The file path pattern is either not set or an empty array in the .meta/config.json file

This means that exercises that had already defined files in the .meta/config.json won't be touched in the PRs.

Note that these PRs are 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 to your track, feel free to ping me on Slack (@ErikSchierboom).

This was referenced Feb 17, 2021
This was referenced Feb 17, 2021
@ErikSchierboom
Copy link
Member Author

There are five open PR's, but none of those tracks (z3, system-verilog, forth, io, nix) have exercises. So I'm comfortable closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant