You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't you love Windows? I'm not even sure if this is an issue, your call. I'm trying to make my library Windows happy so I'm unit testing with Windows paths. When I create an in-memory filesystem and look for a file, the call Stat relies eventually on the internal call "open" which does a map lookup on the result of getData, using the filename as a key. While on many operating systems this behavior is completely reasonable, on some (cough, cough, Windows) it would need to be a case independent compare. Is this something that qualifies as an issue or am I misusing and abusing the in memory filesystem for unholy purposes?
The text was updated successfully, but these errors were encountered:
As far as I can tell you are absolutely correct. You cannot mock case insensitive file systems like the default Windows one with afero. I am having exactly the same issue as you do.
Don't you love Windows? I'm not even sure if this is an issue, your call. I'm trying to make my library Windows happy so I'm unit testing with Windows paths. When I create an in-memory filesystem and look for a file, the call Stat relies eventually on the internal call "open" which does a map lookup on the result of getData, using the filename as a key. While on many operating systems this behavior is completely reasonable, on some (cough, cough, Windows) it would need to be a case independent compare. Is this something that qualifies as an issue or am I misusing and abusing the in memory filesystem for unholy purposes?
The text was updated successfully, but these errors were encountered: