Closed infotroph closed 2 years ago
I guess it's up to you @infotroph and @dlebauer - but agreed that this should be clarified
@infotroph @dlebauer Is this something that should be dealt with soon, like before the next CRAN push? or hold off for a while (that is, should I put it in the milestone for the next CRAN push, or on a later milestone?)
Hold off, this is lower priority On Tue, Mar 21, 2017 at 4:00 PM Scott Chamberlain notifications@github.com wrote:
@infotroph https://github.com/infotroph @dlebauer https://github.com/dlebauer Is this something that should be dealt with soon, like before the next CRAN push? or hold off for a while (that is, should I put it in the milestone for the next CRAN push, or on a later milestone?)
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ropensci/traits/issues/83#issuecomment-288200345, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcX57KVnTsRuJvJwblj-_lJd3sDJ35pks5roCxagaJpZM4L4tY9 .
This repository is about to be archived.
The
id
argument to all BETY functions is currently documented as (emphasis added) "One or more ids for a species, site, variable, etc." But at present no function handles multiple IDs gracefully.In the "plural" functions (eg
betydb_query
), it could make sense to interpret it as an OR operation so thatbetydb_query(id=c(1, 937, 222), ...)
:=betydb_query(id="~^(1|937|222)$", ...)
, but maybe that's too magic and the user should construct the regex themselves if they want it. Also not compatible with v0 API.In the "singular" functions (eg
betydb_specie
) it only makes sense to send one ID per request, so I see two ~reasonable behaviors:betydb_specie(c(1, 2, 3), ...)
:=lapply(c(1, 2, 3), FUN=betydb_item, table="species", ...)
Thoughts, @dlebauer?