Commas in URLs

[Ben-Hodgkiss]

Overview

When adding an endpoint, the parsing to include commas is not working. This is shown by:

• The hash created for the endpoint/source is the same as one without the commas so it seems that the URL being fed into the hash is incorrect.
• When the Github Action runs, it creates too many rows in the file as the URL doesn't seem to go in as a quoted string.

Example
Run this CSV through Manage:
organisation,pipelines,documentation-url,endpoint-url,start-date,plugin,licence local-authority:WIL,article-4-direction,"https://www.wiltshire.gov.uk/planning-conservation-areas#:~:text=plans%20and%20appraisals-,Article%204%20directions,-Most%20residential%20properties","https://maps.wiltshire.gov.uk/arcgis/rest/services/OpenData/Article4Directions/FeatureServer/0/query?where=1%3D1&outFields=Document_url,Documentation_url,Reference,Name&returnGeometry=false&outSR=4326&f=json",2026-03-27,,ogl3

When the Github Action runs, it will show as in this PR: digital-land/config#2456

For the endpoint, you can see that this has created a duplicate with the same hash but different URL (compare rows 229 and 235 in the endpoint CSV on that branch).

This may be related to the Data issue we are having with this endpoint... digital-land/config#2455. Or could be completely separate.

[pooleycodes]

Addressed in digital-land/async-request-backend#99

[pooleycodes]

While debugging a separate issue, I also noticed that the ordering here was incorrect:
digital-land/async-request-backend#100.

The hash was being computed from the parsed URL rather than the raw URL; this has now been corrected by swapping the order.

However, when running the CSV import, the documentation URL suffix appears to be dropped. This likely needs a safer parsed format, as the value passes through the form. Additionally, the URL parsing is duplicated in the Manage Service frontend, which results in duplicated quotation marks in the CSV when copying values.