No Default Custom Method.

[ip312]

Description - What happened? *

In the paramerization section on the consumer side the Custom Method is currenty not set. The field is just empty.

Expected Behavior *

GET method as default.

Observed Behavior *

If a user forgets to select a method, the connector will be stuck in requesting status forever.
To minimize possible errors, it is best to set a default value.

Steps to Reproduce

No response

Context Information

No response

Relevant log output

No response

Screenshots

No response

[tmberthold]

Hello and Thank You for reaching out to us!
Since this is about the UI, I will move this issue accordingly to the ui-repo.
I'll forward it internally and our team will let you know when there's any news.

[jkbquabeck]

Hello @ip312, we changed this presetting to clearly indicate that a user needs to take action to use the parameterization. This This change was necessary since the UI displayed GET before but did not actually select GET as the preset method.

[SebastianOpriel]

Feature itself is no bug, but leads to a bug when no method is chosen, then Connector might lead to an error state.

[AbdullahMuk]

@illfixit proposal to improve this situation: make the first option in the dropdown list as default

[SebastianOpriel]

There was a good reason not to preset GET. Instead please simply make the field mandatory to choose.