It seems we have everything ready, except #48 - Continuous Integration. @ErikSchierboom said he can help with scripts and GitHub Actions, once we implement automated testing of all exercises at once.

pov: update config

pov: update config

At least 20 Practice Exercises are needed to launch track.

checklist:

exercise name (so-called "slug") is linked to a description. task's difficulty is in parentheses. the choice is arbitrary, based on personal reception of exercise description. it's open for discussion/change. this list is chosen randomly from Exercism's problem database. it's sorted by difficulty, and this order should be kept also in config.json.

• [x] hello-world (1) // #7
• [x] two-fer (2) // b2c5112
• [x] reverse-string (1) // #44
• [x] resistor-color (2) // #45
• [x] protein-translation (3) // #47
• [x] space-age (3) // 7f25736
• [x] raindrops (3) // a71ee29
• [x] resistor-color-duo (4) // #46
• [x] rotational-cipher (4) // 67970843
• [x] darts (4) // #53
• [x] largest-series-product (5) // 79a9cf08
• [x] roman-numerals (5) // ffd8763
• [x] resistor-color-trio (6) // #46
• [x] sgf-parsing (6) // #62
• [x] high-scores (7) // 009679130
• [x] run-length-encoding (7) // a836243b3
• [x] simple-linked-list (7) // ccd2b53443
• [x] bowling (8) // 3b68985bc
• [x] pov (8) // 033a49d6f4
• [x] circular-buffer (9) // 097916d

instructions:

1. Comment here to let anybody know which exercises are being worked on,
2. Clone this repo,
3. Run exercise generator:

$ red _tools/generate-practice-exercise.red <exercise-slug>

4. In exercises/practice/<exercise-slug>/<exercise-slug>-test.red change comments like this, to test example solution:

; test-init/limit %exercise-slug.red 1
test-init/limit %.meta/example.red 1

5. Solve exercise example, by editing exercises/practice/<exercise-slug>/.meta/example.red,
6. Run tests. You'll need to change second argument of test-init function from 1 to how many tests you want to run in <exercise-slug>-test.red.

$ cd exercises/practice/<exercise-slug>
$ red <exercise-slug>-test.red

7. Once your solution passes all the tests, remember to revert changes in test-init line: uncomment solution file, comment example file and change limit to 1 (second argument).
8. Change exercise's difficulty in track's config,json. If you want, add practices and prerequisites concepts. Copy exercise's config to proper position, so that all exercises are sorted from easiest to toughest.
9. Make a commit to separate branch and make Pull Requeset.

Just pushed last ex. from the 20 yay!

pov: first function passing tests

pov: all tests passing

pov: first function passing tests

pov: all tests passing

show test output on error

show test output on error

auto-generated files for sgf-parsing exercise

implement sgf-parsing example

Merge branch 'main' into sgf_parsing

🤖 Sync org-wide files to upstream repo (#61)

More info: https://github.com/exercism/org-wide-files/commit/68ae5ebb2706515f915d6e44814827cb4af06732

🤖 Sync org-wide files to upstream repo (#63)

More info: https://github.com/exercism/org-wide-files/commit/f28daf625fa326fafdcf261db7699377c8d1ed37

add sgf-parsing exercise concepts

includes adding a concept for Red/Parse

update authors

Exercise: sgf parsing

Merge pull request #62 from dander/sgf_parsing

concepts in readme's "contributing" section

remove debugging output

largest-serier-product: various error firing methods

remove loziniak as author from dander's exercises

remove debugging output

largest-serier-product: various error firing methods

remove loziniak as author from dander's exercises

concepts in readme's "contributing" section

There's some work started on it: https://github.com/loziniak/red-1/commit/638491ac7e7de6403d76d0fa9220bdb6ccaf9f55

Probably work on concepts should be moved to separate branch, because we don't want to release this track with empty concepts. We should remove all concepts from directory and config on branch main, as well as references to them from practice exercises' practices and prerequisites lists in track's config.json.

auto-generated files for sgf-parsing exercise

implement sgf-parsing example

Merge branch 'main' into sgf_parsing

add sgf-parsing exercise concepts

includes adding a concept for Red/Parse

update authors

Exercise: sgf parsing

Merge pull request #62 from dander/sgf_parsing

I finally got all the tests working.

I added a fair amount more feedback to the test runner to help indicate what is wrong when tests fail. It could be useful for other exercises as well.

I also added an optional test runner argument for the number of tests to run.

One thing I'm a bit uncertain about is that the escaping rules are a bit peculiar (escaped property test). I'm not sure how much of it is assumption of other languages that things like newlines will be represented like \n, but it's a bit awkward for Red. I'm not sure if it would make more sense to convert them to ^/ in the test cases instead...

There are some languages recently added to Exercism, and actively developed. It's good to track their updates: https://github.com/exercism/unison https://github.com/exercism/wasm

Hmm I just found more info in configlet docs , but it suggests, that UUIDs can only be generated by configlet. Perhaps we could just add info about using external tools, and link from everywhere to this page? I can do a PR, but I need an opinion on that before starting to work on it.

Perhaps UUIDs could have their own page in docs, and be linked from all other pages? They cause some confusion, and info on them is spread in documentation, main info on them being in concept exercises section of config.json docs.

There is no central point for concepts. For me it felt natural to just solve exercise examples and look if I could need any new concepts to explain it. So, it seems just as you did with parse. I have some initial work done to start with basics and evaluation concepts. Do you think about working more on concepts? It's a great feature, perhaps we could add concepts one-by-one. There is a task for it: #37 .

UUIDs can be generated offline by hand, they just need to be unique througout the project. You can use configlet for this, or just any online or sytem tool you prefer. Also, during track unit tests, configlet is used to check for uniqueness of UUIDs, so all errors are caught.