Also available, are merge_version and append_version blocks. The merge_version block will compile the possibly multiple versions that would result from the updates inside the block into one summary version. The single resulting version is then tacked onto the version history as usual. The _appendversion block works similarly except that the resulting single version is combined with the most recent version in the history and saved.
My understanding of the explanation is that merge_version will append a single version for all changes made in the block, and append_version will merge all changes into the latest version. Is this how the methods work or is the documentation backwards?
Also available, are merge_version and append_version blocks. The merge_version block will compile the possibly multiple versions that would result from the updates inside the block into one summary version. The single resulting version is then tacked onto the version history as usual. The _appendversion block works similarly except that the resulting single version is combined with the most recent version in the history and saved.
My understanding of the explanation is that merge_version will append a single version for all changes made in the block, and append_version will merge all changes into the latest version. Is this how the methods work or is the documentation backwards?