GithubHelp home page GithubHelp logo

rust-libindy-wrapper's Introduction

rust-libindy-wrapper

LibIndy major artifact of the SDK is a C-callable library that provides the basic building blocks for the creation of applications on the top of Hyperledger Indy, which provides a distributed-ledger-based foundation for self-sovereign identity.

rust-libindy-wrapper is a library for assisting developers using LibIndy API.

rust-libindy-wrapper does not include LibIndy. This will need to be built separately. See IndySDK github

using rust-libindy-wrapper

Assumptions: LibIndy is installed. And, you understand the basics.

Step 1

Add rust-libindy-wrapper to Cargo.toml

[dependencies]
rust-libindy-wrapper = "0.2.13"

Step 2

setup an environment variable that points to LibIndy library. eg:

LIBINDY_DIR="/Users/developer/indy-sdk/libindy/target/release"

Step 3

Use rust-libindy-wrapper. For now, best recommendation is to check out the tests.

License

Released under Apache 2.0 and MIT. See license files in git repo.

rust-libindy-wrapper's People

Contributors

dhh1128 avatar mattraffel avatar mikelodder7 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

rust-libindy-wrapper's Issues

Async methods should return tokio.rs Future

tokio.rs is now "default" solution for asynchronous programming in Rust. It can be quite easy to convert callback to Future with single-shot channel. but 90+% of users will have to write it's own Future based wrapper.

I suggest to change API to return Future instead of callback registration.

Async methods must be default

Instead of wallet::create and wallet::create_async pairs it is better to have wallet::create and wallet::create_sync. Synchronous version is usable for testing or PoC applications only, but we force it as a default.

Module name looks foreign to Rust

I suggest to rename rust_indy_sdk to just indy. SDK is set of tools. This wrapper is for libindy only and in Rust lib is redundant. As result the most correct name is just "indy".

Redundant structs

For the current moment all API functions implemented as static structs methods in dedicated submodule. It causes unnecessary usage of structs in code. We can just have public functions in submodule:

indy::wallet::Wallet::create("{}", "{}").unwrap();

can be just replaced with

indy::wallet::create("{}", "{}").unwrap();

It will look much more nature to Rust.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.