# init(_:editActions:content:) Creates an instance that uniquely identifies and creates views across updates based on the identity of the underlying data. ``` init(_ data: Binding, editActions: EditActions, @ContentBuilder content: @escaping (Binding) -> R) where Data == IndexedIdentifierCollection, ID == C.Element.ID, Content == EditableCollectionContent, C : MutableCollection, C : RandomAccessCollection, R : View, C.Element : Identifiable, C.Index : Hashable ``` ## Parameters `data` The identified data that the [`ForEach`](/documentation/SwiftUI/ForEach) instance uses to create views dynamically and can be edited by the user. `editActions` The edit actions that are synthesized on `data`. `content` The content builder that creates views dynamically. ## Discussion It’s important that the `id` of a data element doesn’t change unless you replace the data element with a new data element that has a new identity. If the `id` of a data element changes, the content view generated from that data element loses any current state and animations. When placed inside a `List` the edit actions (like delete or move) can be automatically synthesized by specifying an appropriate `EditActions`. The following example shows a list of recipes whose elements can be deleted and reordered: ``` List { ForEach($recipes, editActions: [.delete, .move]) { $recipe in RecipeCell($recipe) } } ``` Use [`deleteDisabled(_:)`](/documentation/SwiftUI/View/deleteDisabled(_:)) and [`moveDisabled(_:)`](/documentation/SwiftUI/View/moveDisabled(_:)) to disable respectively delete or move actions on a per-row basis. The following example shows a list of recipes whose elements can be deleted only if they satisfy a condition: ``` List { ForEach($recipes, editActions: .delete) { $recipe in RecipeCell($recipe) .deleteDisabled(recipe.isFromMom) } } ``` Explicit `DynamicViewContent.onDelete(perform:)`, `DynamicViewContent.onMove(perform:)`, or `View.swipeActions(edge:allowsFullSwipe:content:)` modifiers will override any synthesized actions. Use this modifier if you need fine-grain control on how mutations are applied to the data driving the `ForEach`. For example, if you need to execute side effects or call into your existing model code. --- Copyright © 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)