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
As a user of {beekeeper} and API user, it would save me much time and duplicated maintenance effort if there was functionality to search for existing R packages that might serve the API I'm interested in.
{as discussed}
The text was updated successfully, but these errors were encountered:
Code search for the base URL, but it might be somewhat obfuscated in the code (eg https://www.googleapis.com/youtube/v3 might be split into "www.googleapis.com" and "youtube" and "v3" in the code).
Search DESCRIPTIONs for the URL, but again they might not point to a recognizable URL ("https://developers.google.com/youtube/v3" for youtube even though that isn't the actual endpoint, nor the documentation).
So maybe search DESCRIPTION for "API" + a name the user gives?
Ideally I would like to run this as part of spec ingestion. The user might not tell me about the base URL, but the spec will.
Gonna focus on the registry idea for this. I'll use it to encourage people to take on a package. Might make a shinylive app to include in the repo before too long, as a ui onto the list, and then probably link to a Google form to "sign up" for one.
As a user of
{beekeeper}
and API user, it would save me much time and duplicated maintenance effort if there was functionality to search for existing R packages that might serve the API I'm interested in.{as discussed}
The text was updated successfully, but these errors were encountered: