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

Warn on second pretender #178

Merged
merged 2 commits into from
Oct 7, 2016
Merged

Warn on second pretender #178

merged 2 commits into from
Oct 7, 2016

Conversation

trek
Copy link
Member

@trek trek commented Oct 6, 2016

Replaces #156 with a small change.

@coveralls
Copy link

coveralls commented Oct 6, 2016

Coverage Status

Coverage increased (+0.03%) to 97.101% when pulling 87dcbab on warn-on-second-pretender into abff1a6 on master.

@trek trek merged commit 5b95cd7 into master Oct 7, 2016
@trek trek deleted the warn-on-second-pretender branch October 7, 2016 18:31
dustinfarris added a commit to dustinfarris/ember-cli-mirage that referenced this pull request Oct 13, 2016
samselikoff pushed a commit to miragejs/ember-cli-mirage that referenced this pull request Oct 13, 2016
@rwjblue
Copy link
Contributor

rwjblue commented Oct 13, 2016

@trek - This was released without a major version bump (as discussed in #165 (comment)) in 1.4.0... 😿

@shellandbull
Copy link

shellandbull commented Oct 17, 2016

@trek Shouldn't the warning be a console.warn or similar? throwing an error blocks users altogether 😢

kevinansfield added a commit to kevinansfield/Ghost-Admin that referenced this pull request Oct 17, 2016
no issue
- a [recent update](pretenderjs/pretender#178) to Pretender contained a breaking change that throws an error when multiple pretender instances exist
- using mirage in acceptance tests was [triggering the error](miragejs/ember-cli-mirage#915)
@trek
Copy link
Member Author

trek commented Oct 18, 2016

@mariogintili @rwjblue I'm down to do a console.warn instead of throw an error release. I opted not to major bump because certain parts of Pretender (proxy and shutdown) will not work if you start a second server before shutting the first one down.

It was the existing behavior but it's also a bug and doesn't follow the usage requirement we've had since the first release.

I didn't know so many project still relied on this specific bug being left in place.

Azdaroth pushed a commit to Azdaroth/ember-cli-mirage that referenced this pull request Dec 4, 2016
samselikoff pushed a commit to miragejs/ember-cli-mirage that referenced this pull request Dec 9, 2016
kevinansfield added a commit to kevinansfield/Ghost-Admin that referenced this pull request Jan 5, 2017
no issue
- a [recent update](pretenderjs/pretender#178) to Pretender contained a breaking change that throws an error when multiple pretender instances exist
- using mirage in acceptance tests was [triggering the error](miragejs/ember-cli-mirage#915)
acburdine pushed a commit to TryGhost/Admin that referenced this pull request Jan 5, 2017
no issue
- a [recent update](pretenderjs/pretender#178) to Pretender contained a breaking change that throws an error when multiple pretender instances exist
- using mirage in acceptance tests was [triggering the error](miragejs/ember-cli-mirage#915)
kevinansfield added a commit to kevinansfield/Ghost-Admin that referenced this pull request Jan 5, 2017
no issue
- a [recent update](pretenderjs/pretender#178) to Pretender contained a breaking change that throws an error when multiple pretender instances exist
- using mirage in acceptance tests was [triggering the error](miragejs/ember-cli-mirage#915)
acburdine pushed a commit to TryGhost/Admin that referenced this pull request Jan 5, 2017
no issue
- a [recent update](pretenderjs/pretender#178) to Pretender contained a breaking change that throws an error when multiple pretender instances exist
- using mirage in acceptance tests was [triggering the error](miragejs/ember-cli-mirage#915)
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.

None yet

4 participants