[fs][v2] scope-wide requireLiteralLeadingDot config not working

[ayangweb]

The writeFile execution reported an error, I suspect that it is because the path is a path containing a . path, how can I fix this? I am using appDataDir path!

[FabianLars]

Can you also share your configured permissions?

[ayangweb]

{
  "fs:read-files",
  "fs:allow-write-file",
  "fs:allow-copy-file",
  "fs:allow-remove",
  {
    "identifier": "fs:scope",
    "allow": ["**/*"]
  },
}

[ayangweb]

It works fine in macos and windows! Only in linux it reports errors!

[FabianLars]

Yeah, if you only use that scope than the dot is indeed the issue. Either add explicit $APPDATA based scopes or change your existing scope to this

{
  "identifier": "fs:scope",
  "allow": ["**/*"],
  "requireLiteralLeadingDot": false
},

[ayangweb]

Hey👋, requireLiteralLeadingDot set to false also reports the same error!

iShot_2024-10-13_21.55.56.mp4

[FabianLars]

Hmm, that's weird. Just to double check, does ["$APPDATA/*"] work? Also, can you share the function call that's failing?

[ayangweb]

["$APPDATA/*"] also gives an error, also the final export path is chosen by the user, so I wrote ["**/*"].

iShot_2024-10-13_22.04.10.mp4

export const writeFile = (
	path: string,
	data: string,
	options?: WriteFileOptions,
) => {
	const encoder = new TextEncoder();
	const encodeData = encoder.encode(data);

	return tauriWriteFile(path, encodeData, options);
};

await writeFile(getBackupStorePath(), JSON.stringify(content));

[ayangweb]

On macOS and windows, it is normal

iShot_2024-10-13_22.06.40.mp4

[FabianLars]

also the final export path is chosen by the user, so I wrote ["**/*"].

If you use the dialog plugin for that then the scope would be dynamically extended btw, but yeah your solution works too of course.

On macOS and windows, it is normal

Yeah, that's just another argument for the dot being the issue.

I guess the scope-wide requireLiteralLeadingDot setting doesn't work right now then. Try adding this to tauri.conf.json then:

{
  "plugins": {
    "fs": {
      "requireLiteralLeadingDot": false
    }
  }
}