CRATEFIELD
Get started with Harness Join the waitlist

adapter-github-issues

Tracker over the GitHub Issues REST API.

With cargo

cargo add cratefield-adapter-github-issues
crates.iodocs.rsSource

What it is

adapter-github-issues.

The Tracker port over the GitHub Issues REST API for the Cratefield harness (issue #432). It speaks https://api.github.com through the runtime's HttpClient port — no vendor SDK, no reqwest — so the same adapter runs unchanged on Cloudflare Workers and natively (ADR 0002: the port is core's, the vendor client is this crate's).

From the crate’s own README.

Ports

Implements Tracker

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 5 versions recorded, newest first. Every published version is on crates.io.

  1. 0.3.3

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core

  2. 0.3.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
3 earlier versions 0.2.1 to 0.3.1

  1. 0.3.1

    crates.ioReleaseDiff

    Fixed

    • close eight concurrency races across the pool cache, auth caches, realtime rooms, waitlist confirms and tracker adapters (#823)

  2. 0.3.0

    crates.ioReleaseDiff

    Changed

    • Breaking: requires cratefield-core 0.8 (was 0.7), and so a minor rather than a patch bump: a venture still on core 0.7 does not pick this release up through a caret requirement and end up with two copies of core (#712).

    Other

    • updated the following local packages: cratefield-core

  3. 0.2.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core

One of 76 crates in the harness, all of them MIT and all of them in one repository.

Join the waitlist All modules