Confirming how mkdir works

[stackedCG]

Hi tauri devs, just want to confirm this documentation here:

import { mkdir, BaseDirectory } from '@tauri-apps/plugin-fs';
await mkdir('images', {
  baseDir: BaseDirectory.AppLocalData,
});

When I tried using it on the AppData folder it return an error that says that the folder does not exist, now for context I already know that the 'images' does not exist thats why I want to add it, now in order to solve this I delved deep in the documentation with the help of AI and it was solved by adding recursive. Should we add the recursive property in the documentation? Or is this normal, because I thought that just by using the one already on the doc it will work but apparently its not the case.

[FabianLars]

we could at least mention the recursive property there

[stackedCG]

Thank you @FabianLars , but may I know as to why the one in the doc did not work?

[FabianLars]

BaseDirectory.AppData is not the same as the window AppData directory (if that's what you thought). The BaseDirs starting with App are application specific directories (basically means they use your bundle identifier as the dir name) and Tauri does not create any dirs it does not need itself so there's a high chance that AppX directories do not exist until you create them (either explicitly or via the recursive option).

The example in the docs doesn't really care about that behavior though and i guess in this case you could say it assumes you know that already.

[stackedCG]

Thank you for the clarification @FabianLars