WriteMode
public enum WriteMode : CustomStringConvertible, JSONRepresentable
Your intent when writing a file to some path. This is used to determine what constitutes a conflict and what the autorename strategy is. In some situations, the conflict behavior is identical: (a) If the target path doesn’t refer to anything, the file is always written; no conflict. (b) If the target path refers to a folder, it’s always a conflict. © If the target path refers to a file with identical contents, nothing gets written; no conflict. The conflict checking differs in the case where there’s a file at the target path with contents different from the contents you’re trying to write.
-
Do not overwrite an existing file if there is a conflict. The autorename strategy is to append a number to the file name. For example, “document.txt” might become “document (2).txt”.
Declaration
Swift
case add
-
Always overwrite the existing file. The autorename strategy is the same as it is for add.
Declaration
Swift
case overwrite
-
Overwrite if the given “rev” matches the existing file’s “rev”. The supplied value should be the latest known “rev” of the file, for example, from FileMetadata, from when the file was last downloaded by the app. This will cause the file on the Dropbox servers to be overwritten if the given “rev” matches the existing file’s current “rev” on the Dropbox servers. The autorename strategy is to append the string “conflicted copy” to the file name. For example, “document.txt” might become “document (conflicted copy).txt” or “document (Panda’s conflicted copy).txt”.
Declaration
Swift
case update(String)
-
Declaration
Swift
public var description: String { get }