adapter-typesafe

Classifier over TypeSafe's Jev evaluation API, on the operator's own key.

With cargo

cargo add cratefield-adapter-typesafe

What it is

adapter-typesafe.

Classifier port over TypeSafe's Jev evaluation API for the Cratefield harness (issue #456). Runs on the runtime's HttpClient port — no vendor SDK, no reqwest — so the same adapter works on every runtime, the Workers binary included. Bring-your-own-key is the point: the request is billed to the operator's own TypeSafe account, authenticated with the operator's own API key, not a platform-side binding.

From the crate’s own README.

Ports

Implements Classifier

Read more

History

Changelog.

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

  1. 0.3.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
  2. 0.3.1

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core
2 earlier versions 0.2.1 to 0.3.0
  1. 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
  2. 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.