Prevent Selection of a Location on a Layer with no Infoj

[simon-leech]

Prevent Selection of a Location on a Layer with no Infoj

Description

Currently, the location/get method does not check for the presence of an infoj on the locations layer.
This means that its possible to select a location, which then errors as it tries to build a SQL statement in this format
SELECT id, FROM table WHERE id = $1.

This PR addresses this by simply returning if the layer has no infoj, preventing this issue.

Type of Change

Please delete options that are not relevant, and select all options that apply.

• ✅ Bug fix (non-breaking change which fixes an issue)

Testing Checklist

Please delete options that are not relevant, and select all options that apply.

• ✅ Existing Tests still pass
• ✅ Ran locally on my machine

Code Quality Checklist

Please delete options that are not relevant, and select all options that apply.

• ✅ My code follows the guidelines of XYZ
• ✅ My code has been commented
• ✅ Documentation has been updated
• ✅ New and existing unit tests pass locally with my changes
• ✅ Main has been merged into this PR

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1208407306090534

[dbauszus-glx]

Review in progress

[AlexanderGeere]

Added a test for no infoj.

[dbauszus-glx]

This looks good.

I only updated the wording and removed the location from layer.infoj property and made this optional in jsdocs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[RobAndrewHurst]

I am all happy with this.

I added in a test for the getInfoj method so that people can better understand the purpose.