PayloadEditor integration for write operations

[HknLof]

Edit-2: April 20th

The current implementation and state manage follows the approach, that state changes made to the HTML form are synchronized to the payload editor. When changing back form the editor and changes were made, we prompt users to either discard made changes or stay within the editor. If no changes were done, there is no prompt. Generally speaking opening the Edit as JSON button can be found at the bottom of the form.

Exceptions to this rule are the Edit Pipeline window, Edit Config, and New Config containers.

For Edit Pipeline it would have convoluted our pipeline designer. This container already has lots of contents, hence it Edit as JSON is choice before you encounter the Pipeline Designer.

Edit Config and New Config have a slightly special treatment because of the visible tabs. Here, the button Edit as JSON is always visible throughout both tabs.

Will update description with screenshots, once editor draft is implemented.

EDIT-1: Create a second panel for PUT and POST methods ... @flippingbits, will need your guidance to create the same look and feel as ApiCall button. Will implement logic before going into destroying the layout just to fix it again 😄

[HknLof]

@ChrisRousey @flippingbits Grew larger than expected. I did not extract functions for re-use, as this is not being done throughout our UI codebase, [for state management and this references, I guess].

[HknLof]

Thanks for the feedback, I will put this PR to draft and integrate the PayloadEditor into the /**/editcontainers.

[HknLof]

Integrated the <PayloadEditor> into various containers, which perform write operations to our API. Along the way I encountered some issues and housekeeping tasks for our ui implementation, that I would summarize in some tickets.

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information