Closed joenash closed 1 year ago
Hm, our validator is not actually checking if the file is hidden on Windows, is it?
Hm, our validator is not actually checking if the file is hidden on Windows, is it?
Oof, I'll take care of this asap!
The validator should now check for the hidden file on Windows! There were a few other things I caught while testing that I included as well
The description looks good to me! Great work @MarvJohnson :+1:
This PR will close #14. It currently contains the Walkthrough.
This objective is quite different across OSs, due to Windows not using a preceeding
.
for hidden files. In Linux/MacOS, the user simply needs totouch .ahiddenfile.txt
, whilst Powershell users will have to create a new file usingni
, and then hide it usingattrib -h
.The walkthrough as written currently explains the purpose of hidden files, gives a motivated example, and explains the
.
convention to Windows users, who may still encounter it due to cross-platform dev tools. For Windows, it also continues to explain Powershell's linux aliases, this time because in the past we've usedls
to show files, but doing so here will cause an error for Powershell users.