You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2024. It is now read-only.
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 append_version 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?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 append_version 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?
The text was updated successfully, but these errors were encountered: