From 3235b72ef9b49220280dbf7b9c44015ccea1fc0c Mon Sep 17 00:00:00 2001 From: Paul d'Aoust Date: Mon, 8 Apr 2024 14:00:07 -0700 Subject: [PATCH] very tiny edit to clarify that all metadata can be got using get_details --- src/pages/build/entries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/build/entries.md b/src/pages/build/entries.md index bd6a9c7cd..afcca2a18 100644 --- a/src/pages/build/entries.md +++ b/src/pages/build/entries.md @@ -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.