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: Add back outputFile config #59

Merged
merged 1 commit into from
Sep 27, 2015
Merged

fix: Add back outputFile config #59

merged 1 commit into from
Sep 27, 2015

Conversation

dignifiedquire
Copy link
Member

Closes #58

@dignifiedquire dignifiedquire changed the title fix: Add back config fix: Add back outputFile config Sep 3, 2015
@evandavis
Copy link

Why does this automatically nest inside a $browser folder?

@dignifiedquire
Copy link
Member Author

Why does this automatically nest inside a $browser folder?

Because that was the previous behaviour, which I'm trying to restore

erkobridee added a commit to erkobridee/jenkins-ci-and-karma-junit-reporter that referenced this pull request Sep 8, 2015
@SimenB
Copy link
Contributor

SimenB commented Sep 22, 2015

If this restores old behavior, why is it not merged? You broke backwards compatibility in a patch release. Please revert and bump minor (as you're still on 0.x.x (why isn't Karma and it's plugins on 1.x.x btw?)) with this new behavior if it's still wanted.

For us nesting is fine, as we do **/test-results.xml.

Fix for now is of course just to revert to 0.3.3, but that shouldn't be necessary IMO.

@elicwhite
Copy link

@dignifiedquire bump.

@dignifiedquire
Copy link
Member Author

Merging, to restore old behaviour.

dignifiedquire added a commit that referenced this pull request Sep 27, 2015
@dignifiedquire dignifiedquire merged commit 2e5e015 into master Sep 27, 2015
@dignifiedquire dignifiedquire deleted the fix-output-file branch September 27, 2015 17:39
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.

5 participants