Change Details

Designing the UX for editing an existing function. **Acceptance Criteria** [] UX for when a user edits definition [] UX for when a user only edits labels [] UX for how a user would complete multilingual edits [] UX for how Edit Summary works [] Logic for if an input type is changed [] Logic for if an output type is changed [] UX and UI for attach/detach implementations or tests, not editing either **Questions** - In what order will we release a permissions structure? e.g. MVP is anyone can do anything and then we sequentially remove access - What happens when the definition is edited but there are existing implementations? How is this change reflected in the function page? does it need to be reflected elsewhere? - Can anyone detach an implementation from a function? - If I change the type of an input and label, what should happen to the labels in other languages? - If I remove an input, what should happen to the input labels in other languages? Are they automatically deleted? - What should a function that is uneditable look like? This would be for someone with edit permissions. Checkpoints deck: https://docs.google.com/presentation/d/1AFMJACLq0pq3PLZPA7vkZ21Eneztc33-qXSv7h32RvI/edit#slide=id.gf1fddc6d47_0_11 **Features** - Edit summary **Questions** - Who can edit the definition?

This is the ticket for the entire MVP. **Acceptance Criteria** [] User flow for when a user edits definition [] UX for when a user only edits labels [] UX for how a user would complete multilingual edits [] UX for how Edit Summary works [] Logic for if an input type is changed [] Logic for if an output type is changed [] UX and UI for attach/detach implementations or tests, not editing either **Questions** - In what order will we release a permissions structure? e.g. MVP is anyone can do anything and then we sequentially remove access - What happens when the definition is edited but there are existing implementations? How is this change reflected in the function page? does it need to be reflected elsewhere? - Can anyone detach an implementation from a function? - If I change the type of an input and label, what should happen to the labels in other languages? - If I remove an input, what should happen to the input labels in other languages? Are they automatically deleted? - What should a function that is uneditable look like? This would be for someone with edit permissions. Checkpoints deck: https://docs.google.com/presentation/d/1AFMJACLq0pq3PLZPA7vkZ21Eneztc33-qXSv7h32RvI/edit#slide=id.gf1fddc6d47_0_11 **Features** - Edit summary **Questions** - Who can edit the definition?

DesigningThis is the UXticket for editing an existing functionthe entire MVP. **Acceptance Criteria** [] UXUser flow for when a user edits definition [] UX for when a user only edits labels [] UX for how a user would complete multilingual edits [] UX for how Edit Summary works [] Logic for if an input type is changed [] Logic for if an output type is changed [] UX and UI for attach/detach implementations or tests, not editing either **Questions** - In what order will we release a permissions structure? e.g. MVP is anyone can do anything and then we sequentially remove access - What happens when the definition is edited but there are existing implementations? How is this change reflected in the function page? does it need to be reflected elsewhere? - Can anyone detach an implementation from a function? - If I change the type of an input and label, what should happen to the labels in other languages? - If I remove an input, what should happen to the input labels in other languages? Are they automatically deleted? - What should a function that is uneditable look like? This would be for someone with edit permissions. Checkpoints deck: https://docs.google.com/presentation/d/1AFMJACLq0pq3PLZPA7vkZ21Eneztc33-qXSv7h32RvI/edit#slide=id.gf1fddc6d47_0_11 **Features** - Edit summary **Questions** - Who can edit the definition?