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
Copy file name to clipboardExpand all lines: docs/repository-structure.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ Third-party code using the [interface struct crates](#1-interface-struct-crates-
113
113
114
114
**You should create your own customised zome definitions if:**
115
115
116
-
- You wish to combine multiple separate hREA zomes in the same DNA and isolate the storage into different `entry_def` types.
116
+
- You wish to combine multiple separate hREA zomes in the same DNA and isolate the storage into different `entry_type` types.
117
117
- You wish to define private variants of ValueFlows record types or customise sharding and validation rules.
118
118
- You wish to add handling of bespoke organisational logic and related records that needs to be validated tightly against REA data or coordinated as a coherent unit of information.
119
119
@@ -137,7 +137,7 @@ Each module exports an `EntryData` for the record information of relevance, and
137
137
138
138
In cases where records have standard CRUD features, `EntryData` is convertible `From<CreateRequest>` in its associated [interface struct crate](#1-interface-struct-crates-rust-interface); and implements `Updateable<UpdateRequest>` from the [`hdk_records`](#hdk_records) library. These traits are used by [library crates](#3-library-crates-system-core) to handle the underlying storage logic.
139
139
140
-
It is unlikely that there should be a need to create customised versions of these files. For maintenance reasons it is much better to compose additional fields and functionality onto the REA record types as *new*`entry_defs` in zome crates if adding additional fields is a requirement for your use-case.
140
+
It is unlikely that there should be a need to create customised versions of these files. For maintenance reasons it is much better to compose additional fields and functionality onto the REA record types as *new*`entry_types` in zome crates if adding additional fields is a requirement for your use-case.
0 commit comments