New upcoming endpoints /exports and /imports

[alexander-haller]

In GitLab by @mhxion on Jun 13, 2024, 13:13

Nicolas just unofficially confirmed:

Also note that dev version will have an /import and /exports endpoints, so the API will change regarding these concepts.

We would have to keep track, and make sure to update elAPI's list of valid endpoints before these new endpoints are released.

Context: elAPI invalidates (or aborts) if one passes an endpoint name to get, post, patch, delete that elAPI doesn't recognize. So, every time a new endpoint or sub-endpoint is in-development by eLabFTW team, elAPI needs to know. I am beginning think if validating endpoint names were a good idea, though the validation does prevent mistakes quite a lot. This validation was added in !31.

Reported by @alexander-haller. Thanks a lot for paying attention to eLabFTW developments.

[alexander-haller]

In GitLab by @mhxion on Jun 23, 2024, 21:29

Update from Alexander: https://github.com/elabftw/elabftw/commit/3b9b77f6699c94f763b0768ee0f9caa27a33914d.

Some important changes for us:

• [x] New endpoints: import, exports
• [x] /team_tags has moved to teams/{id}/tags. One can replace any calls to team_tags with teams/current/tags. A helpful error message is displayed if the old endpoint is used.

- [ ] sig_keys endpoint moved into users/{id}