Merge pull request #7 from infobip-community/add-email

Add email channel, get SMS logs issue fix

Author: strosek

.gitignore

@@ -17,4 +17,6 @@ Cargo.lock
 
 /.idea/
 /.vscode/
-.swap
+.swap
+
+.env

CONTRIBUTING.md

@@ -62,6 +62,12 @@ Please make sure that all tests and linters pass for all changes. You can check
 We mostly adhere to the [Rust API Guidelines Checklist](https://rust-lang.github.io/api-guidelines/checklist.html) for style and best practices.
 We use `rustfmt` to keep the code well-formatted.
 
+If you made any change that requires updating the readme, please change the lib.rs file, and then generate the README.md file by running the following command:
+```bash
+cargo readme --no-indent-headings > README.md
+```
+And make sure to re-add the nice icons when reviewing the commit diff.
+
 ### ✅ Step 5: Commit
 It is recommended to keep your changes grouped logically within individual commits.
 Many contributors find it easier to review changes that are split across multiple commits.

Cargo.toml

@@ -7,11 +7,12 @@ homepage = "https://www.infobip.com/"
 license = "MIT OR Apache-2.0"
 name = "infobip_sdk"
 repository = "https://github.com/infobip-community/infobip-api-rust-sdk"
-version = "0.2.0"
+version = "0.3.0"
 
 # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
 
 [dependencies]
+dotenv = "0.15.0"
 lazy_static = "1.4"
 regex = "1.6"
 reqwest = { version = "0.11", features = ["blocking", "json", "multipart"] }
@@ -24,8 +25,10 @@ validator = { version = "0.16", features = ["derive"] }
 
 [dev-dependencies]
 httpmock = "0.6"
+chrono = "0.4"
 
 [features]
-default = ["sms", "whatsapp"]
+default = ["sms", "whatsapp", "email"]
 sms = []
 whatsapp = []
+email = []

README.md

@@ -17,21 +17,24 @@ models errors. The module structure is divided by communication channel.
 ## 📡 Supported Channels
 - [SMS](https://www.infobip.com/docs/api/channels/sms)
 - [WhatsApp](https://www.infobip.com/docs/api/channels/whatsapp)
+- [Email](https://www.infobip.com/docs/api/channels/email)
 
 More Channels to be added in the near future!
 
 ## 🔐 Authentication
 To use the library, you'll need to set up an [Infobip account](https://www.infobip.com/signup).
 Then you can use your API Key and custom base URL to call the endpoints. You can use the
 `Configuration::from_env_api_key()` method to load the configuration from the environment. To
-do that, set the `IB_API_KEY` and `IB_BASE_URL` variables.
+do that, set the `IB_API_KEY` and `IB_BASE_URL` variables. Alternatively, you can use the
+`Configuration::from_dotenv_api_key()` method to load the configuration from a `.env` file.
 
 ## 📦 Installation
 To use the library, add the dependency to your projects `Cargo.toml`
 ```toml
 [dependencies]
-infobip_sdk = "0.1"
+infobip_sdk = "<version>"
 ```
+Replace <version> is the latest (or desired) release of the library. For example `0.2.0`.
 
 ## 🚀 Usage
 To use the library, import the client and channel-specific models. Then create a client and
@@ -126,7 +129,7 @@ let message = Message {
 ```
 
 ### Model validation
-Some models have mandatory fields. Optional fields are wrapped in `Option` pointers. Models also
+Some models have mandatory fields. Optional fields are wrapped in `Option` Enums. Models also
 have additional checks to make sure that fields have valid values, when possible. Validation
 is done automatically when calling an endpoint, or you can call the `.validate()` method of the
 model.
@@ -135,7 +138,7 @@ model.
 You can speed up compile time by turning only the needed channels as library features.
 For example, to only build SMS, add the dependency like this:
 ```toml
-infobip_sdk = { version = "0.1", features = ["sms"] }
+infobip_sdk = { version = "0.3", features = ["sms"] }
 ```
 You can see the complete list of features in the Cargo.toml of the project. Feature names
 follow channel names.