Open schloerke opened 2 years ago
I was doing some tests on this too, and can confirm. I can get anything like what we had before working. Its ridiculous behaviour from the API side, imo
One of the main reasons we wanted this function, was to search for all Rladies groups easily, but we could (atleast before) also do that through accessing the pro-account information (needing a pro account token). I can see if I can make any heads or tails of that using the R-Ladies pro account.
I can get anything like what we had before working.
Could you search by the R-Ladies topic_id
and/or retrieve 216 R-Ladies groups by using the find_groups2()
function?
Related: https://github.com/rladies/meetupr/issues/118
Goal: Find all groups for a topic id. Ex:
topicId: 1513883
should return all 140 groups from https://www.meetup.com/topics/r-ladies/all/Limitations: Clicking through the API, we can search for groups via:
filter:
equaling https://www.meetup.com/api/schema/#SearchConnectionFilterThis
SearchConnectionFilter
has support fortopicCategoryId
(ex: Technology,topicCategoryId: 546
). (SearchConnectionFilter
'scategoryId
is for events... this does not make sense to me.)SearchConnectionFilter
does not have support fortopicId
like/find/groups?topicId=1513883
. ðŸ˜Using the
topicCategoryId
of546
and aquery
value ofR-Ladies
, I can find 180 groups.This is pretty solid search results, as there are 40 more results due to some groups not having the
r-ladies
topic ID.Resulting behavior:
{meetupr}
will not be able to search by topic id. 😞 cc @ledell