Yeah, some repos include problem-specifications as a sub-module. Others let the contributor specify the path to their local repository. I believe configlet sync uses its own cached copy of the problem-specs repo so you might be about to hook into that. Likely, the simplest would be for the contributor to specify the path.
Then once we have the problem specs, parsing the tests.toml is fairly straightforward. Match up the names and drop anything that has an include = false line after the description. include = true is the implicit default so itās pretty unlikely weād encounter that. Thereās sometimes a comment field added, but thatās typically to explain why something isnāt included. So you can just check if thereās an include = false somewhere between a test and the next test and then drop that test if so.
argh i pushed an option using the problem specification for the test generator. I will look into the option for specifying the path instead if it will end up being simpler for a contributor.
I managed to mark tests to skip using the current testing library, and also make some commands in the Makefile for generating tests. It works so far it seems, but again I can look at the other option you said above. Any tips are always welcome!
I think we have enough to merge in that first PR. A large part of building out the track will be experimenting with what works and doesnāt work so we can revise as we go.
Hello World only has one test so thereās nothing to skip. We can merge without skipping behavior and then handle it on the next exercise PR where itāll come up organically. Smaller, tightly focused PRs will be easier to review.
Weāre at 28 exercises so far added to the repo. Once the test runner issue is fixed, I think weāre ready for the staff to hook up the infrastructure so the track is available to other maintainers. We still need to write track docs but Iāll work on that this week.
Yes, because the terraform PR has beenāt merged yet (after which the terraform script needs to run). This is done by @ihid, but heās very busy right now.
The Terraform PR still needs to go through for the test runner which requires staff approval. Otherwise, weāre at 32 exercises so weāre looking good. The track docs need to be written, but Iāll be working on that again next week. Once the Terraform stuff goes through, other maintainers can look through the track, and we can get some feedback. Depending on how that goes, we should be ready for launch after that.
Thanks for the update. I have been a little busy myself, so I a have not been as active as I would have liked.
Developer docs wise, I believe the last thing I did was a 1st draft based on your suggestions. When you get a moment, I would appreciate some feedback on that.
I will be much more available now, so if there is anything extra I can do just let me know.
The track docs are all sorted. It looks like the earlier Terraform PR was merged, and the test runner image is available on Docker Hub. I think we still need some internal plumbing sorted since https://exercism.org/tracks/rescript 404s currently. Once thatās resolved, we can start soliciting fellow maintainersā feedback.