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
Many of the functions have a ... argument that gets passed to httr::modify_url() (via npn_GET() and httr::GET()). Possible named arguments include:
scheme = NULL
hostname = NULL
port = NULL
path = NULL
query = NULL
params = NULL
fragment = NULL
username = NULL
password = NULL
There isn't an equivalent to this in httr2 since things like query and path are set with different functions. Are there any common use cases for ... in rnpn code currently? If not, it may make most sense just to deprecate this functionality.
The text was updated successfully, but these errors were encountered:
Currently ... absorb misspelled arguments without any error. Gor example,npn_species_state(state = "AZ", kigndm = "Plantae") returns results for both animals and plants and doesn't error because kigndm gets absorbed by ....
Many of the functions have a
...
argument that gets passed tohttr::modify_url()
(vianpn_GET()
andhttr::GET()
). Possible named arguments include:There isn't an equivalent to this in
httr2
since things like query and path are set with different functions. Are there any common use cases for...
inrnpn
code currently? If not, it may make most sense just to deprecate this functionality.The text was updated successfully, but these errors were encountered: