nickel-org / nickel-postgres Goto Github PK

In line 49 there are two unwrap calls:

self.extensions().get::<PostgresMiddleware>().unwrap().get().unwrap()

Could you explain what will happen if s.th. goes wrong?

With the new error handling just out the door you have to change the return type of your handler to Result<Action, NickelError> and return ok(Continue) instead of just Continue.

//cc @bguiz

Hi!

There are many issues with this crate, latest one not being able to compile Silmukka, since in uses this crate and nickel_cookies crate.

Error Message

native library `openssl` is being linked to by more than one version of the same package, but it can only be linked once; try updating or pinning your dependecies to ensure that this package only shows up once

  openssl-sys v0.7.4
  openssl-sys v0.6.7

This is the main problem I faced and it was easy to fix: remove openssl from nickel_postgres.

Other problems are lack of crates.io package, according to example using crate requires importing many crates (r2d2, postgres, not nickel), which are already present in nickel_postgres.

Is this crate being actively developed, or planned to be? Since I have to fix some of these for Silmukka, should I bother making pull requests?

An error occurred, when I tried to utilize my Nickle with a PostgresMiddleware.

^^^^^^^ the trait `for<'r, 'mw, 'conn> std::ops::FnOnce<(&'r mut nickel::Request<'mw, 'conn>, nickel::Response<'mw>)>` is not implemented for `nickel_postgres::PostgresMiddleware`

Are there going to be any updates anytime soon?