I edited testcase 9 to match the sorting description:
.
|-- much
| `-- amaze
| |-- Hates
| |-- Memes
| `-- Who
`-- such
`-- wow
|-- .much
| |-- pain
| | |-- Dont
| | `-- Suffer
| `-- I
|-- Doge
|-- Love
`-- We
6 directories, 9 files
The previous version was:
.
|-- much
| `-- amaze
| |-- Hates
| |-- Memes
| `-- Who
`-- such
`-- wow
|-- Doge
|-- Love
|-- .much
| |-- I
| `-- pain
| |-- Dont
| `-- Suffer
`-- We
6 directories, 9 files
It should have no incidence on previous solutions cause the case insensitive sort that most people seemed to use in replacement provides the same order than the one described in the puzzle for validators.
The previous solutions will now fail at testcase 9 but itās not a big deal.
Ok. We gonna try to avoid to start another drama here.
I have not solved this puzzle, so I canāt judge personaly of the good of the made changes.
It seems, from what said several users who solved it a long time ago, that the statement and the solution also has been changed. So there are possibly inconsistencies in the puzzle.
However @pardouin , making modifications that can affect the validity of the solutions of many users, is not a thing that can be done ālike thisā, simply saying āI broke all of your codeā on the forum afterwards.
So please keep in mind that:
Any modification to a contribution that is not yours must be notified on the forum AND on the contribution page (Not everyone use the forum).
Any modification that is more important that correcting a typo must be discussed with the author if possible, or with the community.
The āThereās a bug in the puzzleā bias also apply to experimented users. So please think twice before making potentially irreversible changes.
Perhaps that should be added to the guidelines or somewhere @TwoSteps ?
If I posted here about this modification it was mainly to get feedbacks cause Iām aware that impacting previous solutions is not totally harmless.
(I also posted the previous validator so that it can easily be edited back.)
But one sure thing is that the puzzle couldnāt stay as it was.
The other option is to keep the old testcase and modify the description of the sorting process, it wouldnāt affect any previous solution.
I chose the first option cause I didnāt want to alter the original authorās puzzle but I donāt mind if people prefer the second option.
No big issue here. I think youāve been a bit hard with @pardouin
Iām fine with top moderators editing puzzles without prior formal agreement from the author or other players in the community if theyāre sure about their modification.
However:
yes, itās better to notify it in the contribution comments (so at least the author gets a notification and people can check the history of a contrib). Ideally, our system should prompt for a commit message.
yes, it doesnāt hurt to first suggest the change before applying it (even if there is no reaction)
yes, it seems better to modify the description than the testcases since it impacts previous solutions
About the change itself, perhaps @Shoko84 can weigh in?
The author hasnāt started the questmap so it means that heās not active at the moment on CG.
Iāll put back the problematic testcase as it was and change this part of the description:
The tree needs to be sorted in ascending alphabetical order , letters in lowercase having priority on uppercases and without considering the leading and first character ā.ā (dot) from hidden files or directories names.
for this:
The tree needs to be sorted in ascending, alphabetical, case insensitive order and without considering the leading and first character ā.ā (dot) from hidden files or directories names.
This is a good puzzle. It nearly killed me but it is a good puzzle. Iām not sure what was wrong with my earlier attempts, but this time my issue was the logic I used to skip hidden files/directories would miss files that were located in the root directory (i.e. ./.File8 ).
Thanks @5DN1L , I figured out the problem, it was on the sorting part is was not working because of digits. The exemple above is more representative of the problem