upstream API standards and documentation issue

[e-kotov]

The formal OpenAPI spec of the Mapineq API https://mapineqfeatures.web.rug.nl/api.json (human readable https://mapineqfeatures.web.rug.nl/api.html ) does not actually document the endpoints described at https://www.mapineq.org/data-users/ . This prevents the package developers from using tools such as https://github.com/jonthegeek/beekeeper/ to build API adaptors using this spec and instead requires manual reading of the API docs, which makes the job a bit harder.

Update: The new API documentation is actually at https://docs.mapineq.org/api_technical_doc

[jonthegeek]

That's aggravating! It looks like MAYBE you could use beekeeper to build the initial scaffold, call getFunctionsMetaData() (https://mapineqfeatures.web.rug.nl/api.html#/default/getFunctionsMetaData) and/or getFunctionMetaData() (https://mapineqfeatures.web.rug.nl/api.html#/default/getFunctionMetaData) to get details about each function, and then use getFunctionFeatures() as an unexported function called by each of the "real" functions (to let me/{nectar} take care of things like pagination)... but it sounds like you already sorted it out! Sorry the API is annoying!

One of these days I'd like to generalize rapid a bit, and then build tools that can read in some standard documentation formats and produce a rapid object (and then that could be used in beekeeper)... but first I need to finish the basic tooling!

Thanks for the bug report in any case. The step I took to make these APIs work put me on the path toward fixing things for real (if' I'm partially processing the paths in order to get them ready for tibblify, that's a step toward just processing them entirely myself). Good luck with the package!

[e-kotov]

Good luck with the package!

Thanks! And thanks for your work on {beekeper} and related packages! I hope things will get better in automatic API documentation in the future.