object-literal support for `writeStringToFile`?

Configuration Help & General Discussion
,
1

Hi Andreas & BTT community,

I thought that in a previous BTT release the JS bridge for writeStringToFile accepted a single object literal with named properties (e.g. { dataString, path, stringIsBase64 }), but in 5.484 it's not supported. I’m now seeing that only the three-argument, positional form is supported:

// works:
await writeStringToFile('Test 1', output_file_path, false);

// doesn't work:
await writeStringToFile({
  dataString: 'Test 2',
  path: output_file_path,
  stringIsBase64: false
});

According to the current docs, only the positional signature is shown:

writeStringToFile(dataString: String, path: String, stringIsBase64: Bool) async -> Bool
  1. Was the object-literal overload ever officially supported?
  2. If so, was it recently removed or is this an unintended regression?
  3. If not supported, is there any plan to add named-parameter (options-object) support in the future?

I might be mis-remembering the API, but I seem to recall using named properties without issue in an earlier BTT version.