Skip to content

Handle addons with different package names - #46

Merged
rwjblue merged 1 commit into
ember-cli-code-coverage:masterfrom
dfreeman:mismatched-package-names
Oct 7, 2016
Merged

rwjblue merged 1 commit into
ember-cli-code-coverage:masterfrom
dfreeman:mismatched-package-names

Conversation

@dfreeman

Copy link
Copy Markdown
Contributor

This should fix #45, where addons whose name is different from the one in their package.json don't get coverage.

@dfreeman

dfreeman commented Oct 7, 2016

Copy link
Copy Markdown
Contributor Author

Just checking in — anything I can to do help get this merged? We'd love to start using this in a bunch of our internal addons, but right now #45 is a blocker (short of just using a forked version)

@rwjblue
rwjblue merged commit 13630de into ember-cli-code-coverage:master Oct 7, 2016
@rwjblue

rwjblue commented Oct 7, 2016

Copy link
Copy Markdown
Collaborator

Looks great! Sorry for the delay here...

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.

No coverage when addon and package name don't match

2 participants