Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix readConfig bug #65

Merged
merged 1 commit into from
Nov 21, 2016

Conversation

achambers
Copy link
Member

@achambers achambers commented Nov 21, 2016

Fixes #64

This PR will use the new pluginHelper.readConfig function to access config values of this plugin as this.readConfig is no longer a valid function in a config property function.

@lukemelia lukemelia merged commit 9015ac5 into ember-cli-deploy:master Nov 21, 2016
@achambers achambers deleted the fix-read-config-bug branch November 21, 2016 23:30
@@ -48,7 +48,7 @@
"chalk": "^1.0.0",
"core-object": "^1.1.0",
"ember-cli-babel": "^5.0.0",
"ember-cli-deploy-plugin": "^0.2.1",
"ember-cli-deploy-plugin": "^0.2.9",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've been bitten by loose versioning multiple times now. I'm not sure but isn't it better to use a strict version number here. Its ok not to also, perhaps the pros out weigh the cons. Just wanted to pick your brains.

@achambers
Copy link
Member Author

@akshayrawat it js its pros and cons. We're generally very careful about ensuring we don't release breaking changes on minor versions however, we made a mistake this time that slipped through the net. In general though, the loose versioning should be fine here because we control both libs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants