NocoDB integration, normalize URL
kuon opened this issue · comments
When adding a nocodb integration, if the URL is something like https://example.com/
with an ending slash, the API will fails with error like this
"{"msg":"Cannot POST //api/v2/tables/m0oetdcizzz7hze/records"}"
(Notice the double //
)
The same integration works without the final slash in the URL.
I think the URL should be normalized and tolerate the ending slash, as the produced error is cryptic for users that are not developers. Or maybe a test API call should be made before saving the endpoint.