Refine PubChem search parameter passing to align with generic_request patterns

[Copilot]

The PubChem search functions were passing query parameters through an options list wrapper instead of directly via the ellipsis, creating unnecessary nesting.

Changes

• Parameter passing: Changed from generic_request(..., options = options) to do.call(generic_request, c(list(...), query_params)) pattern
• Query parameters: Built dynamically in query_params list, merged directly into function call
• Consistency: Now matches the parameter passing pattern used by cc_search and aligns with how generic_request processes ellipsis arguments (lines 120-127)

Implementation

# Before
options <- list()
if (use_post && input_type == "smiles") {
  options[[input_type]] <- query
}
result <- generic_request(..., options = options)

# After  
query_params <- list()
if (use_post && input_type == "smiles") {
  query_params[[input_type]] <- query
}
result <- do.call(generic_request, c(list(...), query_params))

The functions still use generic_request() with batch_limit = 0 (static endpoint pattern) and leverage httr2 through the abstraction layer as required.

Original prompt

Create a new branch called feat-pubchem-search. I want a new function that will search the PubChem database through the API (https://pubchem.ncbi.nlm.nih.gov/docs/pug-rest#section=Input) and resolved searches for me. There should be a single search request and bulk search request.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.