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

deps: update statuses to v2.0.1 #1480

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

3imed-jaberi
Copy link
Member

No description provided.

@codecov
Copy link

codecov bot commented Jul 14, 2020

Codecov Report

Merging #1480 (f449d84) into master (f3c67d9) will not change coverage.
The diff coverage is 100.00%.

❗ Current head f449d84 differs from pull request most recent head 5af69c8. Consider uploading reports for the commit 5af69c8 to get more accurate results

@@           Coverage Diff           @@
##           master    #1480   +/-   ##
=======================================
  Coverage   99.60%   99.60%           
=======================================
  Files           5        5           
  Lines         507      507           
  Branches      142      142           
=======================================
  Hits          505      505           
  Misses          2        2           
Impacted Files Coverage Δ
lib/context.js 100.00% <100.00%> (ø)
lib/response.js 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f3c67d9...5af69c8. Read the comment docs.

@dead-horse
Copy link
Member

https://github.com/jshttp/statuses/blob/master/HISTORY.md#200--2020-04-19

looks like this upgrade contains incompatible changes

@3imed-jaberi
Copy link
Member Author

Kindly, can you tell me which change is incompatible and I will see what I can do.

@@ -374,7 +374,7 @@ describe('app.respond', () => {
describe('with custom status=700', () => {
it('should respond with the associated status message', async() => {
const app = new Koa();
statuses['700'] = 'custom status';
Copy link
Member

Choose a reason for hiding this comment

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

this is a breaking change for users who want to customize status code

Copy link
Member

Choose a reason for hiding this comment

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

IMO we need to provide a more controllable way to customize status code.

Copy link
Member Author

Choose a reason for hiding this comment

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

this is a breaking change for users who want to customize status code

According to what I understand form you, we should leave this PR to Koa@3 !!

Copy link
Member Author

Choose a reason for hiding this comment

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

IMO we need to provide a more controllable way to customize status code.

Perhaps we can provide a method to store, set, cache.. custom messages for custom codes.

I think this approach is simple and clean.

@3imed-jaberi 3imed-jaberi changed the title deps: update statuses to v2.0.0 deps: update statuses to v2.0.1 Apr 2, 2022
Copy link
Member Author

@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.

Updated to latest version v2.0.1 🚀!

Copy link
Member Author

@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.

@jonathanong @dougwilson @dead-horse @fengmk2
Hello guys, take a look if this is considered as a breaking change you can create a PR for koa v3.x where I can compare it or make a label for v3.x ...!

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

3 participants