Christopher Man
Christopher Man
@bpasero picking this up and working on it now, & will have all unit tests completed.
I created a branch of this repository and working on this issue, I think I have found the issue with the naming convention found within encoding.ts. There seems to be...
Followup, The bug that I found and fixed works on my local dev branch. We'll complete all unit tests to make sure this works, and then we'll submit a PR...
The fix worked and it now renders utf-8-bom encoded filenames !
The above only works when you open the file directly. The issue very much still persists if you open up the file from the file tree. Clearly this is an...
@bpasero @albertosantini The bug is actually a lot more complex than I initially thought. I have found a related issue above, somewhat for a workaround for non-normalized paths, which I'm...
Update: making great progress on this issue, took me some time to map through mentally how the entire file explorer works. Learned significant amount about IPC we use but focusing...
## Update I've identified specifically how we make read directory calls, I initially thought we would make system calls per OS but I see its easily handled via NodejS. Within...
## Update - After running a debugger through all of `pfs.ts` which `readdir()` and `stat()` utilise for async promise file system calls; - I can result that the BOM is...
### Update - I've actually identified where the issue is finally ! #### The Real Problem - When `child.name` contains a BOM character, it causes issues in: - `joinPath(resource, child.name)`...