Feature/enable draft update

[saulipurhonen]

Description

Added option for user to update saved templates.

Related issues

Closes #488

Type of change

• New feature (non-breaking change which adds functionality)

Changes Made

• Template menu action for edit functionality
• Simplified templates list rendering (previous version caused nested tags with form dialog)
• Option for rendering WizardFillObjectDetailsForm component in a dialog
• Form actions for template -typed object
• Reset draftStatus and currentObject redux state objects on form component unmount
• Handle template replace both into backend and redux state
• Prevent re-render of app by moving status message handling rendering logic to message handler from app root
• Serialize status message details
• Updated status message handler tests
• Added test for template edit

Testing

• Integration Tests

[saulipurhonen]

Changes to status message handling had to be made since re-rendering whole app when status message state changes would unmount certain elements, eg. dialogs.

[hannyle]

Looks good to me!

[hannyle]

I've actually encountered this error from Console when updating a template

[saulipurhonen]

I've actually encountered this error from Console when updating a template

Good call. This error was caused because I typed response as optional property for StatusDetails type. Actions need to be serialized and this caused problems when response has nested unserialized data.

Fixed by stringifying response.

[blankdots]

Looks good, just a few notes:

• could be a tad wider
• isn't clear form + update the same as delete. my question would be what would be the use case for clear form ? - we could also omit it

[saulipurhonen]

• could be a tad wider
• isn't clear form + update the same as delete. my question would be what would be the use case for clear form ? - we could also omit it

Good points. I think we could change the width once we're doing whole design overhaul.

Not sure if "Clear form" button is needed. Could there be some use cases where user would want to use the template id but re-fill the form?

May be we could prevent updating empty form?

[blankdots]

Good points. I think we could change the width once we're doing whole design overhaul.

ok

Not sure if "Clear form" button is needed. Could there be some use cases where user would want to use the template id but re-fill the form?

May be we could prevent updating empty form?

let us remove clear form, I don't see a use case for it, and if we find one we will add it back
And yes we should prevent empty form, it there is the case, but do you mean prevent in front-end or back-end ?

[saulipurhonen]

let us remove clear form, I don't see a use case for it, and if we find one we will add it back And yes we should prevent empty form, it there is the case, but do you mean prevent in front-end or back-end ?

I mean preventing empty form in front-end which is in the matter of fact implemented already.