Update empc_ftxt() to indicate 1 input limit #55
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
epmc_ftxt()
only works with one PMCID. Currently, it attempts to execute with more than one PMCID and fails. In the example below 2 good PMCIDs are passed, first together then separately. Only when they are given separately does it work.Created on 2023-11-17 by the reprex package (v2.0.1)
The current documentation appears to indicate
epmc_ftxt()
can accept multiple inputs and the test to ensureext_id
is correctly formatted will pass as long as the first element ofext_id
starts with 'PMC' (all others are ignored with a warning).This PR depluralizes the documentation and updates the
ext_id
argument test to ensure it allows only one PMCID.Loosely related to #38 and #37.
It seems like the documentation for
europepmc
functions are written in plural while primarily accepting singular inputs, so I totally understand if the documentation updates are dropped. Theext_id
test update alone would still avoid malformed API requests and the need for user debugging.