Currently, when the node operator is in the edit journey, if he goes to the Sub-chain page and change the sub-chain name, the name won't get saved because we don't have a "on change" listener attached to the input.
Description
Currently, when the node operator is in the edit journey, if he goes to the Sub-chain page and change the sub-chain name, the name won't get saved because we don't have a "on change" listener attached to the input.
Requirements
We need to attach an "on change" listener which gets fired after 500ms (we nee a delay here, otherwise we would make DB calls as the node operator types, not ideial). There is an example on the UI Kit project, svc-event-emitter component.
Acceptance criteria
All the items must be sorted following the requirements. If something isn't clear, please reach out to the team as soon as possible.
User Story
Currently, when the node operator is in the edit journey, if he goes to the Sub-chain page and change the sub-chain name, the name won't get saved because we don't have a "on change" listener attached to the input.
Description
Currently, when the node operator is in the edit journey, if he goes to the Sub-chain page and change the sub-chain name, the name won't get saved because we don't have a "on change" listener attached to the input.
Requirements
We need to attach an "on change" listener which gets fired after 500ms (we nee a delay here, otherwise we would make DB calls as the node operator types, not ideial). There is an example on the UI Kit project, svc-event-emitter component.
Acceptance criteria
All the items must be sorted following the requirements. If something isn't clear, please reach out to the team as soon as possible.