22NULL
33
44# ' Entrez identifier sets
5- # '
5+ # '
66# ' Many Entrez APIs accept either a UID list or tokens that point to a result stored
77# ' on its history server. The classes here wrap these and keep track of the
88# ' database name that the identifiers belong to. Most of the API helpers in this
99# ' package are generic over the type of ID set and so can be used the same way with
1010# ' either type. For large numbers of UIDs, the web history versions are generally
1111# ' recommended to avoid running into server-side request timeouts.
12- # '
12+ # '
1313# ' `id_list` is a vector and can be manipulated to take subsets (e.g. `id_set[1:10]` or
1414# ' `tail(id_set)`).
15- # '
15+ # '
1616# ' `web_history` is an opaque reference to an ID list stored on the Entrez
1717# ' history server. Through the course of API calls, information about the length or
1818# ' the actual list of IDs may be discovered and cached, avoiding subsequent API calls.
1919# ' `as_id_list()` can be used to extract the list of IDs.
20- # '
20+ # '
2121# ' Convert `id_list` to `web_history` with [`epost()`].
2222# ' Convert `web_history` to `id_list` with `as_id_list()`.
23- # '
23+ # '
2424# ' @rdname id_set
2525# ' @param db name of the associated Entrez database (e.g. `"biosample"`).
2626# ' @param ids UIDs, coercible to a character vector (can be accessions or GI numbers).
@@ -192,7 +192,7 @@ check_compatible_db <- function(
192192}
193193
194194# ' Check ID set is well formed
195- # '
195+ # '
196196# ' @param x ID set object.
197197# ' @param database name of intended database.
198198# ' If `NULL` the database name is not checked.
@@ -217,7 +217,7 @@ check_id_set <- function(
217217 }
218218
219219 if (! is.null(database )) {
220- actual_db <- entrez_database(x )
220+ actual_db <- entrez_database(x )
221221 if (database != actual_db ) {
222222 cli :: cli_abort(c(
223223 " {.arg {arg}} is an ID set from the wrong Entrez database" ,
0 commit comments