Chorus is a Rust library which poses as an API wrapper for Spacebar Chat, Discord and our own Polyphony. Its high-level API is designed to be easy to use, while still providing the flexibility one would expect from a library like this.
You can establish as many connections to as many servers as you want, and you can use them all at the same time.
Chorus combines all the required functionalities of an API wrapper for chat services into one modular library. The library handles various aspects on your behalf, such as rate limiting, authentication and maintaining a WebSocket connection to the Gateway. This means that you can focus on building your application, instead of worrying about the underlying implementation details.
To get started with Chorus, import it into your project by adding the following to your Cargo.toml file:
[dependencies]
chorus = "0.18.0"To connect to a Polyphony/Spacebar compatible server, you'll need to create an Instance like this:
use chorus::instance::Instance;
#[tokio::main]
async fn main() {
let instance = Instance::new("https://example.com", None)
.await
.expect("Failed to connect to the Spacebar server");
// You can create as many instances of `Instance` as you want, but each `Instance` should likely be unique.
dbg!(instance.instance_info);
dbg!(instance.limits_information);
}This Instance can now be used to log in, register and from there on, interact with the server in all sorts of ways.
Logging in correctly provides you with an instance of ChorusUser, with which you can interact with the server and
manipulate the account. Assuming you already have an account on the server, you can log in like this:
use chorus::types::LoginSchema;
// Assume, you already have an account created on this instance. Registering an account works
// the same way, but you'd use the Register-specific Structs and methods instead.
let login_schema = LoginSchema {
login: "[email protected]".to_string(),
password: "Correct-Horse-Battery-Staple".to_string(),
..Default::default()
};
// Each user connects to the Gateway. Each users' Gateway connection lives on a separate thread. Depending on
// the runtime feature you choose, this can potentially take advantage of all of your computers' threads.
let user = instance
.login_account(login_schema)
.await
.expect("An error occurred during the login process");
dbg!(user.belongs_to);
dbg!(&user.object.read().unwrap().username);All major desktop operating systems (Windows, macOS (aarch64/x86_64), Linux (aarch64/x86_64)) are supported.
wasm32-unknown-unknown is a supported compilation target on versions 0.12.0 and up. This allows you to use
Chorus in your browser, or in any other environment that supports WebAssembly.
To compile for wasm32-unknown-unknown, execute the following command:
cargo build --target=wasm32-unknown-unknown --no-default-featuresThe following features are supported on wasm32-unknown-unknown:
| Feature | WASM Support |
|---|---|
client |
✅ |
rt |
✅ |
rt-multi-thread |
❌ |
backend |
❌ |
voice |
❌ |
voice_udp |
❌ |
voice_gateway |
✅ |
We recommend checking out the "examples" directory, as well as the documentation for more information.
Rust 1.70.0. This number might change at any point while Chorus is not yet at version 1.0.0.
Make sure that you have at least Rust 1.70.0 installed. You can check your Rust version by running cargo --version
in your terminal. To compile for wasm32-unknown-unknown, you need to install the wasm32-unknown-unknown target.
You can do this by running rustup target add wasm32-unknown-unknown.
In general, the tests will require you to run a local instance of the Spacebar server. You can find instructions on how to do that here. You can find a pre-configured version of the server here. It is recommended to use the pre-configured version, as certain things like "proxy connection checking" are already disabled on this version, which otherwise might break tests.
To test for wasm, you will need to cargo install wasm-pack. You can then run
wasm-pack test --<chrome/firefox/safari> --headless -- --target wasm32-unknown-unknown --features="rt, client, voice_gateway" --no-default-features
to run the tests for wasm.
Like other cargo crates, this crate uses Semantic Versioning 2.0.0 as its versioning scheme. You can read the specification here.
Code gated behind the backend feature is not considered part of the public API and can change without
affecting semver compatibility. The backend feature is explicitly meant for use in symfonia
See CONTRIBUTING.md.