Struct dropbox_sdk::files::UploadArg
source · #[non_exhaustive]pub struct UploadArg {
pub path: WritePathOrId,
pub mode: WriteMode,
pub autorename: bool,
pub client_modified: Option<DropboxTimestamp>,
pub mute: bool,
pub property_groups: Option<Vec<PropertyGroup>>,
pub strict_conflict: bool,
pub content_hash: Option<Sha256HexHash>,
}dbx_files only.Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.path: WritePathOrIdPath in the user’s Dropbox to save the file.
mode: WriteModeSelects what to do if the file already exists.
autorename: boolIf there’s a conflict, as determined by mode, have the Dropbox server try to autorename
the file to avoid conflict.
client_modified: Option<DropboxTimestamp>The value to store as the client_modified timestamp. Dropbox automatically records the
time at which the file was written to the Dropbox servers. It can also record an additional
timestamp, provided by Dropbox desktop clients, mobile clients, and API apps of when the
file was actually created or modified.
mute: boolNormally, users are made aware of any file modifications in their Dropbox account via
notifications in the client software. If true, this tells the clients that this
modification shouldn’t result in a user notification.
property_groups: Option<Vec<PropertyGroup>>List of custom properties to add to file.
strict_conflict: boolBe more strict about how each WriteMode detects conflict. For example, always
return a conflict error when mode = WriteMode::Update and the given
“rev” doesn’t match the existing file’s “rev”, even if the existing file has been deleted.
This also forces a conflict even when the target path refers to a file with identical
contents.
content_hash: Option<Sha256HexHash>A hash of the file content uploaded in this call. If provided and the uploaded content does not match this hash, an error will be returned. For more information see our Content hash page.