Docs don't match released version

[mfeckie]

The README currently refers to config/content-security-policy.js, but having recently installed this addon and having problems with config not being detected, I dug around and found that the installed version 1.1.1 doesn't include the new code required to read from the config file.

[jelhan]

Yeah, sorry. We are in the middle of a refactoring of the configuration. The readme reflects the current master not the last release. Please refer to readme for the version used. E.g. you could access the readme for v1.1 with this link: https://github.com/rwjblue/ember-cli-content-security-policy/blob/v1.1.1/README.md

[rwjblue]

Sorry this bit you @mfeckie. FWIW, this is a really common problem and folks should generally read the docs of the version they are using. Unfortunately, GH doesn't make that easy (though NPM does a decent job of displaying the README's in that case).

[RobbieTheWagner]

Is there an ETA on a new release? I just hit this issue as well.

[jelhan]

Is there an ETA on a new release? I just hit this issue as well.

We are planing to do a first release candidate soon. See #100 for details.

[wongpeiyi]

Got hit by this as well. Maybe adding a note in the readme would help

[jelhan]

Closing as v2.0.0 has been released finally.