Skip to content

Commit

Permalink
very tiny edit to clarify that all metadata can be got using get_details
Browse files Browse the repository at this point in the history
  • Loading branch information
pdaoust committed Apr 8, 2024
1 parent e8fc6c9 commit 3235b72
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion src/pages/build/entries.md
Original file line number Diff line number Diff line change
Expand Up @@ -207,7 +207,7 @@ Calling `update_entry` does the following:

### Update patterns

Holochain gives you this `update_entry` function, but is somewhat unopinionated about how it's used. You can interpret an update as applying to either the original _action_ or the original _entry_ being updated, because the `Update` action is merely a piece of metadata attached to both, and can be retrieved along with the original data.
Holochain gives you this `update_entry` function, but is somewhat unopinionated about how it's used. You can interpret an update as applying to either the original _action_ or the original _entry_ being updated, because the `Update` action is merely a piece of metadata attached to both, and can be retrieved along with the original data using [`hdk::prelude::get_details`](https://docs.rs/hdk/latest/hdk/prelude/fn.get_details.html) (see below).

You can also choose where to attach updates. You can structure them as a 'list', where all updates refer to the `ActionHash` of the original `Create` action.

Expand Down

0 comments on commit 3235b72

Please sign in to comment.