MCPcopy Create free account
hub / github.com/Vector35/binaryninja-api / upload_database

Method upload_database

rust/src/collaboration/project.rs:892–908  ·  view source on GitHub ↗

Upload a file, with database, to the remote under the given project `metadata` - Local file with database `parent_folder` - Optional parent folder in which to place this file `name_changeset` - Function to call for naming a pushed changeset, if necessary

(
        &self,
        metadata: &FileMetadata,
        parent_folder: Option<&RemoteFolder>,
        name_changeset: C,
    )

Source from the content-addressed store, hash-verified

890 /// * `parent_folder` - Optional parent folder in which to place this file
891 /// * `name_changeset` - Function to call for naming a pushed changeset, if necessary
892 pub fn upload_database<C>(
893 &self,
894 metadata: &FileMetadata,
895 parent_folder: Option<&RemoteFolder>,
896 name_changeset: C,
897 ) -> Result<Ref<RemoteFile>, ()>
898 where
899 C: NameChangeset,
900 {
901 // TODO: Do we want this?
902 // TODO: If you have not yet pulled files you will have never filled the map you will be placing your
903 // TODO: New file in.
904 if !self.has_pulled_files() {
905 self.pull_files()?;
906 }
907 sync::upload_database(self, parent_folder, metadata, name_changeset)
908 }
909
910 /// Upload a file, with database, to the remote under the given project
911 ///

Callers 2

upload_new_fileMethod · 0.80
test_project_syncFunction · 0.80

Calls 3

upload_databaseFunction · 0.70
has_pulled_filesMethod · 0.45
pull_filesMethod · 0.45

Tested by 1

test_project_syncFunction · 0.64