Allows using a proper struct instead of a tuple in arguments, which should make things a bit clearer and more type-safe. Doing the same for return values may require changing napi itself so that will have to come later.
IBVCQSSGPKLQTD4T4TAJZRC4LY3G6FP4QWFEBHN5KEFI44ZGGAXQC ) -> Result<(vscode_sys::reference::SourceControlRef,vscode_sys::reference::SourceControlResourceGroupRef,vscode_sys::reference::SourceControlResourceGroupRef,),napi::Error,> {let arguments = FnArgs::from((uri, pijul_label, changes_label, untracked_label));
) -> Result<initialize_source_control::Return, napi::Error> {let arguments = initialize_source_control::Arguments {repository_uri_ref,pijul_label,changes_label,untracked_label,};
let (repository_uri_ref, pijul_label, changes_label, untracked_label): Arguments =function_call_context.args()?;
let (external,): (&External<Arguments>,) = function_call_context.args()?;let Arguments {repository_uri_ref,pijul_label,changes_label,untracked_label,} = &**external;
let unrecorded_changes = source_control.create_resource_group("changes", &changes_label)?;let untracked_paths = source_control.create_resource_group("untracked", &untracked_label)?;
let unrecorded_changes = source_control.create_resource_group("changes", changes_label)?;let untracked_paths = source_control.create_resource_group("untracked", untracked_label)?;