Skip to content

2.7.1.md

Latest commit

 

History

History
16 lines (11 loc) · 1.3 KB

2.7.1.md

File metadata and controls

16 lines (11 loc) · 1.3 KB
Raw
summary toArray tolerates JSON-stringified array arguments from LLM callers — get_field_values fields no longer silently wraps a stringified array into one bogus element
breaking false
security false

2.7.1 — 2026-06-14

Changed

  • toArray (query-helpers) parses a [-leading string that JSON.parses to an all-string array into that array, rather than scalar-wrapping it. Any string that fails to parse, or parses to a non-string-array, falls through to the prior scalar-wrap — every legitimate scalar (status/phase enums, NCT IDs, PascalCase field names) starts with a letter, so a [-leading value is always a stringified array or garbage. Overloads keep required call sites typed string[]. (#75)
  • get_field_values fields and get_study_results nctIds route their one-or-many normalization through toArray instead of an inline Array.isArray check. (#75)

Fixed

  • get_field_values fields no longer wraps a JSON-stringified array ('["OverallStatus","Phase"]') into a single bogus element that fails downstream with an opaque upstream error. (#75)