Inconsistent client-side and server-side validation for URL metadata fields

[rolodato]

How are you running Flagsmith

• Self Hosted with Docker
• Self Hosted with Kubernetes
• SaaS at flagsmith.com
• Some other way (add details in description below)

Describe the bug

URL metadata fields are validated serverside to have a scheme and authority per

flagsmith/api/metadata/models.py

Line 60 in 1dfcdc2

return all([result.scheme, result.netloc])

However, client-side a scheme is not mandated, and an error is not shown in this case.

Steps To Reproduce

1. Save a URL metadata field with a valid value like https://example.com
2. Try to update the value to example.com

Changes are not saved because the API rejects a URL without a scheme like example.com as invalid, but the UI doesn't mark the same value as invalid. Other invalid values like example are correctly rejected by both API and UI.

Expected behavior

Validation for URLs should behave the same way in the UI and API. I would prefer keeping the API's validation logic to always make URL schemes explicit in whatever custom field data we're storing.

Screenshots

No response