HTTP Verb Dropdown Read-Only When API Endpoint Type is Custom: Static

[Tshepiso-R]

Bug Description

When configuring Form Settings, changing the API Endpoint Type to Custom: Static causes the HTTP Verb dropdown to become read-only and default to GET. Users are unable to change the HTTP verb to other options such as POST, PUT, or DELETE.

---

Steps to Reproduce

1. Navigate to any Form.
2. Click on the Settings button.
3. Change API Endpoint Type to Custom: Static.
4. Observe the HTTP Verb field.

---

Actual Behavior

• The HTTP Verb dropdown is disabled/read-only.
• The value defaults to GET.
• Users cannot select any other HTTP verb.

---

Expected Behavior

• The HTTP Verb dropdown should remain editable.
• Users should be able to select any supported HTTP verb (GET, POST, PUT, DELETE, etc.) when using Custom: Static endpoints.

---

Screenhshot

Additional Notes

This also affects release 0.44

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Error while planning edits - (🔄 Check again to try again)

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Button ReadOnly property #3925
• Checkbox group allows selection on render in Read-only mode when selection mode is multiple #3994
• Deleting a configuration form on the frontend throws a 401 unauthorized error while the user is logged in #2301
• Endpoints fail due to missing required fields #2867
• Endpoint fails when re-updating a form with a readOnly property without refreshing the page #2449

👤 Suggested Assignees

• hlayisanimazuze
• hlakudi200
• Mluleki03

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!