Bug/optional geospatial component submit data

[davidjamesstone]

Proposed change

While doing the ticket I noticed there was a bug that caused the submission to fail when sending optional Geospatial fields where the user hadn't added any features. The submit sent the value as undefined which caused a schema validation failure given it expects a string. This PR replaces undefined with an empty string which aligns with what FileUpload sends when optional.

Jira ticket: https://eaflood.atlassian.net/browse/DF-1157

Type of change

• Bug fix
• New feature
• Breaking change
• Misc. (documentation, build updates, etc)

Checklist

• You have executed this code locally and it performs as expected.
• [] You have added tests to verify your code works.
• You have added code comments and JSDoc, where appropriate.
• There is no commented-out code.
• You have added developer docs in README.md and docs/* (where appropriate, e.g. new features).
• The tests are passing (npm run test).
• The linting checks are passing (npm run lint).
• The code has been formatted (npm run format).

[jbarnsley10]

Worth adding a test in case future code breaks it? Approving anyway

[davidjamesstone]

Worth adding a test in case future code breaks it? Approving anyway

Resolved with d911ad5

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud