Avoid merging policies in build time configuration

[jelhan]

Should be backward-compatible as it still merges the policy object set by contentSecurityPolicy runtime config.

Closes #99

[jelhan]

@sandstrom This is ready to be reviewed and merged from my side.

[jelhan]

@rwjblue Seems like sandstorm is busy. Would be great if you have some time for a review.

[rwjblue]

LGTM, this will be a major bump, right (since it changes merging behaviors)?

[jelhan]

LGTM, this will be a major bump, right (since it changes merging behaviors)?

It only changes merging behavior for policies that are defined using new configuration but not for legacy configuration. There wasn't any release yet that includes new configuration. So it should be backward compatible. There is also a test that legacy configuration is merged, which isn't touched by this PR: https://github.com/rwjblue/ember-cli-content-security-policy/blob/2266d1a7bba293af4330459b0ffb9c94a3042fee/node-tests/unit/config-test.js#L53-L74

[jelhan]

Please have a look at #100 for a proposal for next release. The main idea is to use the altered configuration interface as a backward-compatible toggle for new defaults. It lists the changes that should be bundled together to prevent the need of a breaking change.

[rwjblue]

It only changes merging behavior for policies that are defined using new configuration but not for legacy configuration. There wasn't any release yet that includes new configuration. So it should be backward compatible.

Awesome, thank you. I'm sorry I missed that.