better story then my restricted chars kata lol :D

Merged.

It's like the brain is trying to explain the inconsistencies that occur in a dream.

It's a very long explanation for "Don't type keys twice" :p But otherwise pretty funny :p

Your solution is not far from correct, I managed to get it pass all tests after changing a line or two. You are basically missing this part in your solution:

Upper case letters will count as their lower case counterpart, not being able to write "Aa".

The fork needs to be approved, otherwise the Dart version will continue to operate under the old rules.

I removed them because they are not special anymore. There is no extra requirements related to spacing, so spaces are now treated just like any other character. This is why I think that explicit tests for spacing are not necessary anymore. Even more, multi-space tests were not even generated by random tests in original translations, before I changed them.

Fork Dart
I made some edits, now it looks like the Python version

I noticed you removed these two tests: " a " and "1 1 1" I don't quite understand why they were deleted.

The tests in the Basic Tests and Sentence Test blocks are duplicated.

I went throung all current languages, added targeted tests, removed unnecessary reqiurments, and unified all langs. You can now go over your Dart translation and adapt it to new requirements, or I can fix it myself, whichever you prefer.

You can use any of existing languages as an example. If you find any issues, let me know.

gutted and stuffed an octopus left unattended

I removed tests for None, and added tests with hopefully better coverage.

I did not remove tetss for spaces, because I do not think that this requirement is very bad, and it also requires changes to description, which I prefer to do in a full sweep after fixing more relevant things.

I will work on java nad kotlin version tomorrow. Feel free to take a look at the current Python version and let me know if there's something you do not like.

By duplicate test, I mean this:
Python tests typically return something like this:
dvKYzUecEYTqHIphGOsfnHFJRasRpQsJVuozRpwMrucNdMvgnp should equal 'dvKYzUecEYTqHIp*GOsfnH*JRas*pQ*JVuozRpwMrucNdMvgnp'

Dart tests return something like this:
'AAT1FFNhm7FHFFFyFZ FJYFF8FQFFxqPFF?FoFi ZFFzfF F IsFF8FFFFF FF GBFF FF FFFOT wF' --> 'A*T1F*Nhm7FH***yFZ *JY**8FQ**x*PF*?*o*i ZF**** *F Is**8*F*** ***GBF* ***F**OT w*'

As you can see, duplicate characters are rare and are far away; there is no test that specifically generates such cases.

I plan to update the tests in a way they guarantee complete coverage. It sohuld be easy now as there are only three languages, and pending ones should be easy to adapt. I can approve them right after changing existing languages, and I can adapt them myself to new rules too.

imo what we should be doing here is to:

• remove the null/space test from dart
• fix the dart case with the long fixed case which uses undefined behaviour (click me to view) and is not correctly quoted (your null is also quoted suggesting it's a string which it isn't, but if that's getting removed then it doesn't need to be fixed)
• someone else can update python to add same or similar tests with numbers (I don't know what you mean by duplicates though, there are repeated letters so ..)
• remove the mention of spaces-only from description
• create issue for java/kotlin to remove null/space