The goal of this ticket 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.

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

• If user has permission, allow user to edit definition,
• If user does not have permission to edit definition, communicate that
• Allow user to edits labels
• Allow user to complete multilingual edits
• If user has permission, allow them to change input type or count
• If user has permission, allow them to change output type

[] If user has permission, allow them to publish implementation drafts
[] If user has permission, allow them to deactivate published implementations
[] If user does not have permission to publish implementations or deactivate published implementations, communicate that
(these last three are moved to view function ticket)

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

Design details

• 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 is edited, that edit is propagated throughout the other languages.

Not in scope

• UI for functions that are not editable
• Notifications for edits
• Watchlists
• Edit implementations UI or UX