Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move out bindings #295

Open
5 tasks
clehner opened this issue May 10, 2022 · 0 comments
Open
5 tasks

Move out bindings #295

clehner opened this issue May 10, 2022 · 0 comments
Labels
developer experience Make nicer and easier to use for developers

Comments

@clehner
Copy link
Contributor

clehner commented May 10, 2022

Like didkit-go and didkit-python, the other DIDKit language bindings/FFIs and their examples should be moved out into separate repos, which would each depend on the didkit Rust crate.

Moving out the bindings should help simplify this repo and improve CI build times. In particular, removing the "Build Android Archive" CI step would reduce the per-commit CI run time here by half (~30 minutes).

Possibly the C FFI can be kept in the didkit crate, since it is relied on in multiple places (Dart/Flutter, iOS/Swift, and Android/JNI). However, those should probably each depend on language-specific bindings for async support (#287) rather than using the blocking C functions.

Bindings to move out

  • Android + JNI
  • iOS/Swift
  • Dart/Flutter
  • WASM (Web + Node.js)
  • Node.js (Neon)
@clehner clehner added the developer experience Make nicer and easier to use for developers label May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer experience Make nicer and easier to use for developers
Projects
None yet
Development

No branches or pull requests

1 participant