ElasticEmail 4.2.0

Official Rust SDK for the Elastic Email REST API v4
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69

# Contributing to the Elastic Email Rust SDK

Thanks for taking the time to contribute! This document explains how to report problems, suggest changes and submit pull requests.

## Before you start: this SDK is generated

Almost everything in this repository (`src/apis`, `src/models`, `docs/`, `Cargo.toml` and most of `README.md`) is generated by [OpenAPI Generator](https://openapi-generator.tech) from the Elastic Email API specification.

This means:

- **Manual edits to generated files will be overwritten** by the next release.
- If an endpoint, model, parameter or description is wrong or missing, the fix belongs in the API specification. Please [open an issue](https://github.com/ElasticEmail/elasticemail-rust/issues/new/choose) describing the problem. We'll fix it upstream and regenerate the SDK.
- Pull requests are most useful for non-generated content: documentation, examples, tests, build and CI configuration, and repository tooling.

If you're not sure whether something is generated, open an issue first and ask.

## Reporting bugs

Search [existing issues](https://github.com/ElasticEmail/elasticemail-rust/issues) first. If nothing matches, open a new issue using the **Bug report** template and include:

- SDK version (the Git tag in your `Cargo.toml`, e.g. `4.2.0`)
- Rust version (`rustc --version`) and OS
- The API function you called and a minimal code sample
- The full error: for `Error::ResponseError`, the HTTP status (`status`) and response body (`content`)

**Never paste your API key** into an issue, log or code sample.

Questions about your Elastic Email account, sending limits, deliverability or billing aren't handled in this repository. The preferred way to get help is the **chat widget on [elasticemail.com](https://elasticemail.com)**.

Looking for sample code? See the [Elastic Email examples repository](https://github.com/ElasticEmail/elasticemail-examples), including the [Rust examples](https://github.com/ElasticEmail/elasticemail-examples/tree/main/rust-elasticemail-examples).

## Suggesting features

Open an issue using the **Feature request** template. Describe the use case first and the solution second. It helps us decide whether the change belongs in the API, the SDK or the documentation.

## Security issues

Please do **not** report security vulnerabilities in public issues. See [SECURITY.md](SECURITY.md).

## Development setup

Requirements: [Rust](https://www.rust-lang.org/tools/install) 1.75 or later, with Cargo.

```bash
git clone https://github.com/ElasticEmail/elasticemail-rust.git
cd elasticemail-rust
cargo build
cargo test
```

The crate uses edition 2021. Don't add new runtime dependencies without discussing it in an issue first.

## Pull requests

1. Fork the repository and create a branch from `master` (`git checkout -b fix/short-description`).
2. Keep each change focused. One logical change per pull request.
3. Make sure `cargo build` and `cargo test` pass.
4. Update documentation if your change affects how the SDK is used.
5. Open a pull request against `master` and fill in the template.

A maintainer will review your pull request and may ask for changes. When a change touches generated code, we may apply it upstream instead of merging the PR directly. You'll still get credit in the release notes.

## Code of Conduct

This project follows the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you agree to uphold it.

## License

By contributing, you agree that your contributions will be licensed under the [MIT License](LICENSE).