Skip to content

fix: allow metadata probes on path lookups - #11

Merged
sabino merged 3 commits into
mainfrom
fix/path-parameter-metadata-sync
Aug 12, 2026
Merged

fix: allow metadata probes on path lookups#11
sabino merged 3 commits into
mainfrom
fix/path-parameter-metadata-sync

Conversation

@sabino

@sabino sabino commented Aug 12, 2026

Copy link
Copy Markdown
Owner

What changed

  • treat an unbound path-template endpoint as an empty parameterized lookup
  • keep equality-bound path lookups issuing the same live HTTP request
  • verify unbound probes make no outbound request
  • add and package a real 0.3.1 to 0.3.2 PostgreSQL extension upgrade
  • install every initial and upgrade SQL file from native archives

Why

Catalog and BI clients probe declared JSON fields with an unfiltered scan. A
path endpoint such as /items/{id} cannot make a valid request until id is
bound, and the previous hard error aborted the client field synchronization.
Returning an empty relation is conservative, preserves the declared tuple
descriptor, avoids a fake/default identifier, and performs no network work.

Validation

  • cargo fmt --all -- --check
  • Python and browser JavaScript syntax checks
  • shell syntax checks
  • native archive contract test
  • native installer contract test
  • YAML parsing
  • cargo metadata --locked --no-deps
  • full PostgreSQL 14 through 18 integration matrix
  • full control-plane integration workflow

@sabino
sabino merged commit d5c1d47 into main Aug 12, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant