Skip to content

feat: align async STAC resolver with Python client - #11

Closed
Faolain wants to merge 1 commit into
mainfrom
agent/native-async-stac-parity
Closed

feat: align async STAC resolver with Python client#11
Faolain wants to merge 1 commit into
mainfrom
agent/native-async-stac-parity

Conversation

@Faolain

@Faolain Faolain commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

What changed

  • Export the existing asynchronous STAC CID resolvers from the package root and document direct resolver usage.
  • Share one bounded pagination implementation between CID resolution and catalog listing.
  • Reject cross-origin, credential-bearing, and unsupported-method pagination links.
  • Disable automatic redirect following and avoid forwarding server-provided continuation headers over plaintext HTTP.
  • Detect repeated pagination requests and use all search pages when listing datasets.
  • Add focused resolver/listing parity tests and repository-level guidance for keeping the Python and JavaScript clients aligned.
  • Bump the package version from 0.6.0 to 0.7.0.

Why

The JavaScript client was already asynchronous and already used the resolver internally, so Python event-loop pooling and explicit client cleanup do not apply. However, the resolver was not exported from the package root, catalog listing stopped after one page, and pagination did not have the request hardening added in dClimate/dclimate-client-py#16.

Impact

Consumers can resolve a CID directly through the public package API. Existing high-level loading behavior is unchanged. Resolver and listing pagination now have the same trust boundary and bounded-walk behavior as the Python client, adapted to the platform-owned fetch transport.

Validation

  • npm run lint: passed
  • Focused STAC suite: 26 passed
  • npm run build: browser and Node builds passed
  • Full suite attempted: 195 passed and 13 live integration tests failed because the current external IPFS/catalog data timed out or now requires an explicit grouped-Zarr level; the focused unit suite is green.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 0401672e-8e0c-4416-8d91-0cd1ea2f3745

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@0xSwego

0xSwego commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Closing this connector-authored draft so it can be recreated under the required 0xSwego identity.

@0xSwego 0xSwego closed this Aug 6, 2026
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.

2 participants