Skip to content

v2.7.4: geoFilter site re-ranking, multi-valued field flag, concise parse errors

Choose a tag to compare

View all tags
@cyanheads cyanheads released this 21 Jun 23:59
v2.7.4
This tag was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.
8ebf003
This commit was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.

geoFilter site re-ranking, multi-valued field flag, concise parse errors

Added:

  • search_studies: with an active geoFilter, each study's locations[] is re-ranked by proximity to the filter center so the matched site leads and renders with distanceMi; sites without a geoPoint are kept (re-rank only, never filter). New shared geo-helpers.ts (#84)
  • get_field_values: array-typed fields (Phase, Condition) carry multiValued: true plus a format() note, so callers don't read the per-value buckets as a percentage of the corpus (#85)

Fixed:

  • search_studies / get_study_count: query parse errors no longer leak the raw Essie/ANTLR grammar dump — the offending token is extracted and the 'expecting {…}' list dropped, recovery hint retained (#83)

550 tests pass; bun run devcheck clean.

Assets 3
Loading