#Go: Instructions for simple_cipher appear to be incorrect

46 messages ยท Page 1 of 1 (latest)

unborn ocean
#

Step 3 requires us to create a random 100-char key for vigenere if the key is empty:

If someone doesn't submit a key at all, generate a truly random key of at least 100 lowercase characters in length.

and nowhere in the instructions is there mention of a minimum key length.

However, the tests require the function to return nil for any key < length 3, including length 0.

tribal schoonerBOT
sullen estuary
#

In general, the tests are the exercise requirements and needing to run the tests to discover all the requirements is working as intended.
#1082698079163134073 is meant for help solving an exercise, and not as a platform to discuss exercises.

unborn ocean
#

@sullen estuary I understand, but I do not use discourse and github issues are disallowed. Do you have another suggestion on how to provide feedback?

#

I'm happy to stop providing feedback as well if that's better. Doesn't matter either way to me.

grim tusk
unborn ocean
#

@grim tusk what is the exercism forum? I thought that was discourse.

grim tusk
#

Please re-read very first response to your question by @tribal schooner ๐Ÿ™‚

unborn ocean
#

@grim tusk Yes. forum.exercism.org is discourse. I do not use discourse (please read my response to Isaac).

grim tusk
#

You have an exercism account, right?

#

With your exercism account you can use the exercism forum

#

I don't understand what you mean with "I do not use discourse". Do you mean "discord" when saying "discourse"?

unborn ocean
#

you don't understand. It's not that I can't use it, I choose not to.

grim tusk
#

oh you don't want to use the forum. ok

unborn ocean
#

that.

#

so there's no other place to suggest changes / report bugs other than discourse and here. If I can't do it here, then I'll just stop doing it. No biggie.

grim tusk
#

you can report bugs via the ... in the top right corner

#

fyi

unborn ocean
#

where's that menu?

grim tusk
#

inside the exercise, in the code editor. on the right side

unborn ocean
#

I don't see it. but I don't use the code editor.

grim tusk
unborn ocean
#

mine looks completely different.

grim tusk
#

click on the "Open in Editor" button

#

for the simple cipher exercise

unborn ocean
#

ah, so you have to actually be IN the editor. Gotcha.

#

I do all of mine locally so I don't see that menu.

#

Where does that get posted?

grim tusk
#

ยฏ_(ใƒ„)_/ยฏ

#

๐Ÿ˜…

unborn ocean
#

if it goes to discourse then that's not ok.

#

eh, too complicated. I'll just wait for github issues to be permitted again. Appreciate the help though!

grim tusk
#

github PRs get auto rejected, did you get your github issue to be not auto rejected?

unborn ocean
#

no.

#

that's my point: github got shut down and the alternative (discourse) doesn't work for me, so I was hoping that I could use discord (here) to report issues, but apparently that's not allowed. So there's no way for me to report issues.

fickle mango
#

a lot of people (maintainers) still prefer the forum because it is easier to keep track, slower pace and they themselves don't use discord

#

as for the exercise itself, despite the introduction text and the problem specs. sometimes maintainer chose to implement extra test (either to enforce something, or adding new tests to match with the introduction)
so when I did this exercise for powershell track, I add tests that actually check for the random generated key that mentioned above. some tracks dont have it, but it's fine because they still follow the specs

#

in the case of the go track, that might be the key regarding the minimum key len test. so there are 2 ways you can deal with this imo

  1. the test suite is the authoritative source for an exercise (which is what we often say to learners), which mean unless something really wrong and contradict the spec/ intruction, you follow the test suites
  2. ask for an appendix for exercise for the go track. which you dont seem like you want to do
unborn ocean
#

@fickle mango I understand. The problem is that the readme instructions conflict with the tests. That's all.

#

if you follow the readme, your tests will fail.

sullen estuary