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

response.redirect: extract special-cased back, fixes #904 #1115

Merged
merged 2 commits into from
Oct 20, 2024

Conversation

fl0w
Copy link
Contributor

@fl0w fl0w commented Dec 27, 2017

The simple solution to drop special-cased 'back' in response.redirect.
I can't label but should be labeled as version-major.

This PR does not make use of Symbol as purposed in #904.

Edit
If this solution is acceptable, a deprecation should be added to Koa 2 on 'back' use.

@codecov
Copy link

codecov bot commented Dec 27, 2017

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.47%. Comparing base (b89e19a) to head (ad03d65).
Report is 18 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1115      +/-   ##
==========================================
- Coverage   99.61%   99.47%   -0.14%     
==========================================
  Files           5        7       +2     
  Lines         520      575      +55     
  Branches      147      165      +18     
==========================================
+ Hits          518      572      +54     
- Misses          2        3       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@fl0w
Copy link
Contributor Author

fl0w commented Dec 28, 2017

I'm assuming this is a travis-cache thingie that fails, can't reproduce it locally.

$ git rev-parse --abbrev-ref HEAD
refactor-back
$ node -v
v9.3.0
$ npm -v
5.6.0
$ npm view koa version
2.4.1
$ npm t

# abbreviated jest output

Test Suites: 66 passed, 66 total
Tests:       298 passed, 298 total
Snapshots:   0 total
Time:        2.265s
Ran all test suites.

@jonathanong
Copy link
Member

👍

let's add this as a feature + deprecation message, then a separate PR to remove it in the next major version

@fl0w
Copy link
Contributor Author

fl0w commented Feb 15, 2018

@jonathanong updated, and should be safe as a semver-minor merge. Just take a quick look at the deprecation message before doing so.

lib/response.js Outdated Show resolved Hide resolved
Copy link
Member

@3imed-jaberi 3imed-jaberi left a comment

Choose a reason for hiding this comment

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

LGTM, I believe that should be merged this PR 🚀

@kevinpeno kevinpeno force-pushed the refactor-back branch 2 times, most recently from a231946 to aa5f75b Compare October 20, 2024 22:54
@kevinpeno
Copy link
Contributor

@jonathanong should be gtg. Codecov is bitching, but the related missed line is not related to the changes made in this PR. It is likely the methods added to this PR pushed the file over its limits. I think we should ignore it for this PR.

@kevinpeno kevinpeno self-assigned this Oct 20, 2024
@jonathanong jonathanong merged commit f9f7714 into koajs:master Oct 20, 2024
5 of 6 checks passed
@iwanofski
Copy link

I couldn't see this update because this was done om my "stolen" account :) Great to see this merged.

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

Successfully merging this pull request may close these issues.

6 participants