You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation showcases the API endpoint of vo.registry.search, all the while, the top level namespace provides the same as regsearch.
I think this is a rather unfortunate and possibly confusing setup and we should instead aim to avoid providing multiple API endpoints for the same functionality.
OTOH, if people feel strongly for the need of vo.regsearch, then we should make that the official API endpoint and rework all the docs to use that, and only that.
The text was updated successfully, but these errors were encountered:
The documentation showcases the API endpoint of
vo.registry.search
, all the while, the top level namespace provides the same asregsearch
.I think this is a rather unfortunate and possibly confusing setup and we should instead aim to avoid providing multiple API endpoints for the same functionality.
OTOH, if people feel strongly for the need of
vo.regsearch
, then we should make that the official API endpoint and rework all the docs to use that, and only that.The text was updated successfully, but these errors were encountered: