Describe the Bug
In the REST DSL editor's Add REST Method dialog, the HTTP Method field is initialized with get.
When a user types the exact valid value post and confirms it with Enter, the dropdown closes and the field appears to contain post, but the underlying operation remains get. After adding the operation, the REST tree and generated Camel REST DSL show GET instead of POST.
Selecting post by clicking the option in the dropdown works correctly. This makes the keyboard interaction misleading because it visually accepts a valid method without persisting it.
Expected behavior: confirming the exact post option with Enter updates the model and creates a POST operation.
Actual behavior: the visible input shows post, but the initialized get value remains in the model and a GET operation is created.
Workaround: open the dropdown and click the post option with the mouse.
Steps to Reproduce the Bug or Issue
- Open the REST DSL editor.
- Create or select a REST service.
- Choose Actions → Add Operation.
- In HTTP Method, replace the default
get value by typing post.
- Press Enter to confirm the exact matching option.
- Enter a path and ID, then click Add.
- Inspect the operation in the REST tree or generated Camel YAML.
The operation is created as GET, although the dialog appeared to accept post.
Repeat the same steps, but select post by clicking it in the open dropdown. The operation is then correctly created as POST.
Screenshots or Videos
A recording can be provided if needed. The important comparison is:
- Type
post + press Enter → operation remains GET.
- Click the
post dropdown option → operation becomes POST.
Platform
- OS: macOS
- Browser: Chromium-based embedded browser
- Kaoto version: 2.11.0
@kaoto/forms version: 1.8.0
Found while embedding Kaoto in another application, but the behavior is in Kaoto's REST DSL editor/typeahead interaction. Report prepared with AI assistance and reviewed by a human, following the project's CONTRIBUTING.md guidance.
Describe the Bug
In the REST DSL editor's Add REST Method dialog, the HTTP Method field is initialized with
get.When a user types the exact valid value
postand confirms it with Enter, the dropdown closes and the field appears to containpost, but the underlying operation remainsget. After adding the operation, the REST tree and generated Camel REST DSL showGETinstead ofPOST.Selecting
postby clicking the option in the dropdown works correctly. This makes the keyboard interaction misleading because it visually accepts a valid method without persisting it.Expected behavior: confirming the exact
postoption with Enter updates the model and creates a POST operation.Actual behavior: the visible input shows
post, but the initializedgetvalue remains in the model and a GET operation is created.Workaround: open the dropdown and click the
postoption with the mouse.Steps to Reproduce the Bug or Issue
getvalue by typingpost.The operation is created as
GET, although the dialog appeared to acceptpost.Repeat the same steps, but select
postby clicking it in the open dropdown. The operation is then correctly created asPOST.Screenshots or Videos
A recording can be provided if needed. The important comparison is:
post+ press Enter → operation remainsGET.postdropdown option → operation becomesPOST.Platform
@kaoto/formsversion: 1.8.0Found while embedding Kaoto in another application, but the behavior is in Kaoto's REST DSL editor/typeahead interaction. Report prepared with AI assistance and reviewed by a human, following the project's CONTRIBUTING.md guidance.