[boyska]

If you're adding a new endpoint make sure that

• The new entry is at the correct (alphabetically sorted) line.
• The endpoint is valid according to https://validator.spaceapi.io/ui — it shows an error about the address not being valid, but it's just that indeed the hacklab is in such a place which doesn't have a "proper" address :)

[rnestler]

Contrary to your declaration it fails both the sorting check and the validation check:

--- directory.json
+++ directory.json
@@ -9,8 +9,8 @@
   "Amman Valley MakerSpace": "https://raw.githubusercontent.com/AmmanVMS/space.api/main/api.json",
   "Apollo-NG": "https://apollo.open-resource.org/status.php",
   "Arch Reactor": "https://archreactor.org/status.php",
-  "AvANa": "https://avana.forteprenestino.net/spaceapi.json",
   "Attraktor Makerspace": "http://blog.attraktor.org/spaceapi/spaceapi.json",
+  "AvANa": "https://avana.forteprenestino.net/spaceapi.json",
   "AwesomeSpace": "https://state.awesomespace.nl/",
   "B4CKSP4CE": "https://spaceapi.0x08.in/",
   "Bastli": "https://bastli.ethz.ch/spaceapi.json",

validation:

For the validity: 0.13 required to have the state field always present. By just declaring
"api_compatibility": ["14", "15"], and removing "api": "0.13", it should be fixed.

[boyska]

Contrary to your declaration it fails both the sorting check and the validation check:

ooops, fixed

validation:

For the validity: 0.13 required to have the state field always present. By just declaring "api_compatibility": ["14", "15"], and removing "api": "0.13", it should be fixed.

thanks for letting me understand what was the problem! I assumed it was something about the Geo coordinates, because that was the most prominent warning I could understand (and it is irrelevant in our case).

now everything should be fixed.

[rnestler]

thanks for letting me understand what was the problem! I assumed it was something about the Geo coordinates, because that was the most prominent warning I could understand (and it is irrelevant in our case).

Yeah missing keys are handled very badly by the validator UI: They are just not shown, since it tries to show error messages next to the key they affect (which doesn't exist if the key is missing). I needed to dig into the browser dev tools and look at the validator API response.