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
Describe the bug
In order to resolve #113 on Windows OS, the io.isHidden function has been added to abstract away the details for determining if a filepath points to a hidden file:
This function is meant to be a temporary shim to circumvent the fact that the hidefile package currently fails when attempting to read file attributes on Windows OS platforms (see stevenvachon/hidefile#3). There are currently no alternative packages that are known to properly read file attributes on Windows OS, so until the hidefile package is patched this issue will remain open.
Versions (please complete the following information):
This issue is no longer relevant and has been superseded by switching to using find-up::findUp instead of isomorphic-git::findRoot in getRoot in v3.0.0. Per the discussions in #359, the issue was primarily occurring when the getRepoRoot function (now called getRoot) would read an empty directory on Windows. This appeared to have been occurring when getStatus was called, which is now also transitioned to using git directly instead of isomorphic-git.
Describe the bug
In order to resolve #113 on Windows OS, the
io.isHidden
function has been added to abstract away the details for determining if a filepath points to a hidden file:synectic/src/containers/io.ts
Lines 51 to 58 in c0f9457
This function is meant to be a temporary shim to circumvent the fact that the
hidefile
package currently fails when attempting to read file attributes on Windows OS platforms (see stevenvachon/hidefile#3). There are currently no alternative packages that are known to properly read file attributes on Windows OS, so until thehidefile
package is patched this issue will remain open.Versions (please complete the following information):
development
)Additional context
The
io.isHidden
function was added in #359, and additional discussion details can be found within that PR.The text was updated successfully, but these errors were encountered: