Hugo Firth

@pauljamescleary Out of interest - as this is intended to be an example of a production scala application, why not go for a scala.js front end e.g. using [scala-js-react](https://github.com/japgolly/scalajs-react) and...

Well I'm afraid I don't know the other frameworks mentioned, so I'll just start slowly chipping away at a scala-js-react app in a fork (probably next week) and let you...

Hi Guys, I just wanted to jump in here and say that I have seen this. Unfortunately I am completely flat out at the moment and so haven't had time...

@fmendoza Can you give me some more details? What is the code inside the `try` block. What input are you giving where you expect the error?

@rycastaneda No there isn't - could you not set it the same way you would any other config value however? http://laravel.com/docs/configuration

Correct. I prefer to specify 2.0.\* versions so that I try and ensure breaking changes like this don't happen -.-

I'm in unfamiliar territory here. I'm keen not to break the rules of semantic versioning. Is it worth tagging a bug fix release in which the dependency is shifted to...

Hi @rikless To be honest I haven't encountered this issue myself and so have no sure fire way to cope with it. This package could do with a little TLC...

Hi @nikbora & @kyrpas I see that the latest tagged release of the mailchimp/mailchimp package is 2.0.5. If reverting back solves your issue then by all means do it for...

@nikbora how in your usage does 2.0.3 throw up any other bugs? I'm considering tagging a bug fix release with the hard dependency on that earlier version, and then tagging...