Here's my attempt at this for #3 !

The crux is leveraging the failure crate.

I was not able to eliminate unwrap in the following:

• DocumentCollection::index
• DocumentCollection::index_mut
• Model::from_document
• Model::to_document
• All instances of unwrap in tests remain

Additionally, I was not able to figure out how to run all the tests as they seemed to be interfering with each other. So, each test uses it's own database.

Feedback and modifications welcome! 😀

With new update to 0.5.2, the readme still showed 0.5.1. Instead of changing it, it is better to stick to "0.5" (as "0.5" means "^0.5.0" it shouldn't be a problem). The only issue is you have breaking changes from 0.5.x to the 0.5.(x+1) then the users have to specify the entire version.

Your FOSSA integration was successful! Attached in this PR is a badge and license report to track scan status in your README.

Below are docs for integrating FOSSA license checks into your CI:

• CircleCI
• TravisCI
• Jenkins
• Other

In the codebase, there are 66 occurences of unwrap(), including most of them panicking if there's a problem with SSL/Requests.

Cleaning up will take place in 0.6.0 since it might break the API a bit (eg: returning Result<T, E> instead of T)

Hi,

We're using your excellent library in one of our solutions. We did have to make some changes to integrate it into the tokio async framework. The library has been "upgraded" to use the latest serde and reqwest libraries.

We've also added some examples to illustrate the use of the library.

Kind regards, Marcel

Hi, I just updated from reqwest 0.8.x to 0.9.x to be able compile sofa in my dev environment running on Ubuntu 18.04 LTS and Arch Linux without any issues regarding the version of the OpenSSL library. Please review my code changes. I'm not so familiar with Rust yet. Thank you. Kind regaards, Tobias

fixes #6 this is a real basic implementation, i'm not too familiar with reqwest or couchdb. It's enough for my use case, but I expect this to need some love before it can be merged.

what is the purpose of the get_self(...) method on Client?

    pub fn get_self(&mut self) -> &mut Self {
        self
    }

it returns a mutable reference to self, but you can only call the method if you already have a mutable reference to self.

fixes #7 I've made most of the functions generic over the input they actually need, rather than concrete types. I think there's still some work to be done to improve the api.

this is a minor breaking change as seen below-

before

fn example(s: String) {
   let x: String = s;
}

fn main() {
   let my_str : &'static str = "example string";

  // this won't compile after the change as type ascriptions would be required to determine how to apply 'into()'
   example(my_str.into())
}

after

fn example<S: Into<String>>(s: S) {
   let x: String = s.into();
}

fn main() {
   let my_str : &'static str = "example string";

  // consumer of library can now use any type which can be converted into a concrete string to call the function
   example(my_str)
}