Documentation request: current folder files entry

[david-morris]

The onFolderChange callback is called with an empty path when the component first loads, so it can't be used to request fetching a new list of files.

Am I missing what it's supposed to be used for? I wouldn't want a flash if I was using it for synchronizing UI somewhere else, either.

Ultimately, I'm left with no way to handle the current path.

Edit: I noticed in the source that you're supposed to have the current directory listed. Additionally, it needs its real name and not "." I'll adjust my code accordingly, but that should probably be noted in the docs.
I also experimentally determined that it expects paths to start with a folder name, not "/". Again, it would save time if this was documented.

[Saifullah-dev]

@david-morris By default, the initial path is set to root directory ("") unless specified through initialPath prop e.g. initialPath="/Documents".

Here's a guide to handle current path:

const [currentPath, setCurrentPath] = useState("/Documents"); 

<FileManager
  // other props...
  initialPath={currentPath}
  onFolderChange={setCurrentPath}
/>

I'll add this info in documentation as well.
Please note that initialPath is only set once on the initial files load.

PS. I noticed onFolderChange is also invoked on the initial files load. If you use this callback to fetch files on demand, it may result in redundant initial fetches — this behavior will be fixed in this release.

[Saifullah-dev]

🎉 This Fix is included in version 1.26.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release