Best way to comment on an exercise with bad instructions?

I’m doing the Swift track, and I’ve run into a couple small things where the instructions don’t quite line up with the tests. Right now I’m on the Poetry Club exercise, and its instructions are just outright missing things and/or wrong in ways I needed to dig into the tests and code (exemplar on GitHub) to find.

What’s the best way to let Exercism know about such issues so as to get them resolved?

For this specific exercise, the instructions for the front and back door passwords do not say to return "_" for an empty input string; and the back door instructions specifically say to append ", please." (with the period), but the tests check for ", please" (without the period).

Because of those omissions and errors this exercise is literally impossible to finish strictly following just the instructions given. If I run into any more issues as egregious as this I’d like to let the team know so they can be addressed.

The best way to give feedback is here on the forum, via the track-specific category. For the Swift track, see Swift - Exercism

2 Likes

This exercise was forked from the Javascript track. Comparing the two sets of files, it does look like periods were introduced in the Swift exercise instructions. I’m not the maintainer, but I think the examples in the docs should be updated rather than the tests to avoid invalidating already completed solutions.

The ”_” part appears only in the Swift implementation and should probably be documented in the instructions. Students can’t see the tests for a concept exercise without working offline or checking GitHub so I sympathize with your frustration there.

Also, since this isn’t in the Swift forum, the maintainer might not be seeing this thread so I’m CCing @Meatball just in case.