The goal of this epicticket is to manage the design and testing of the edit function work flow and UI. When an editor wants to edit an existing function, they can only do so through the function editor. They can edit any part of the function definition, implementations, or testers. Once they edit the function, they must publish their work for the edits to be saved.
**Acceptance Criteria**For the MVP we are assuming all users have permissions to make any edit. We are also assuming that all edits will immediately publish without need of any special authorization.
# Acceptance Criteria
[] User flow for when a user edits definition
[] User flow when a user only edits labels
[] User flow for how a user would complete multilingual edits
[] Design notes for if an input type is changed
[] Design notes for if an output type is changed
[] UX and UI for attach/detach implementations or tests, not editing either
[] UX for how Edit Summary works
# Deliverables
**Deliverables**
- High-level mockups for mobile and desktop with interaction design notes
- Mock ups for one RTL language for key screens
- Mock ups for long character length languages for key screens
**Not in scope**
- UI for functions that are not editable# Design details
**Notes**
- We- We will release a permissions structure by sequentially removing/restricting access to features and actions
-. For now anyone can detach an implementation from a function and edit any aspect of the function definition.
- If the input type is changedis edited, that changeedit is propagated throughout the other languages
- If an input is removed, that change is propagated throughout the other languages.
# Not in scope
- UI for functions that are not editable
- Notifications for edits
- Watchlists