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

docs: document http-terminator (fixes #1096) #1097

Merged
merged 1 commit into from
Apr 3, 2020

Conversation

gajus
Copy link
Contributor

@gajus gajus commented Jan 20, 2020

No description provided.

Copy link
Member

@jonchurch jonchurch left a comment

Choose a reason for hiding this comment

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

Edit: I've requested one change, but otherwise...
LGTM 👍
This package actually looks quite good too btw, kudos!

P.S. the failing CI doesn't have anything to do with this PR.

The CI was failing before this PR, but there is one styling error introduced by it, which I suggested a change on. ❤️

Copy link
Member

@jonchurch jonchurch left a comment

Choose a reason for hiding this comment

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

Thanks! LGTM

@gajus
Copy link
Contributor Author

gajus commented Jan 27, 2020

Do I need to do anything regarding the failing tests?

@jonchurch
Copy link
Member

@gajus Nope, that's not a blocker and there's a PR #1094 open that will fix the failing CI.

This is pending review from @expressjs/expressjs-com and after that it will likely get merged in.

@wesleytodd
Copy link
Member

This is not a judgement on the package, but I would like to see the express documentation have less documentation on third party packages. Today there is a ton of outdated stuff which was added years ago, and I would like to not make it any worse. I think we should consider moving stuff like this into an "awesome list" format instead of it being on the express website. Thoughts about this direction @jonchurch?

@gajus
Copy link
Contributor Author

gajus commented Feb 15, 2020

I think we should consider moving stuff like this into an "awesome list" format instead of it being on the express website.

What makes that different from the current format?

@wesleytodd
Copy link
Member

We wouldn't maintain it :) The problem with it on the website is it makes us already limited maintainers have more work. In an awesome list I, and I am guessing the other primary maintainers would not maintain it.

@jonchurch
Copy link
Member

I think having a discussion about cleaning up the site would be fruitful. IMO the site should document the project and not much else.

However, as things stand we do have these kind of sections and I think OP’s library is high quality so Im pro merging.

These kinds of sections (recommendations of libraries) can always be removed in the future, and I think it would be pragmatic to move towards that.

Copy link
Contributor

@dougwilson dougwilson left a comment

Choose a reason for hiding this comment

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

I know there was a bunch of conversation in this PR revolved around the greater idea on 3-rd party modules, but they are there today, and this one is really nice, so I'm going to merge it in and if there is ever a policy in the future, it's easy to adjust the contents at that time 👍

@dougwilson dougwilson closed this in 41256a9 Apr 3, 2020
@dougwilson dougwilson merged commit 41256a9 into expressjs:gh-pages Apr 3, 2020
@github-pages github-pages bot temporarily deployed to github-pages April 3, 2020 04:03 Inactive
@gajus
Copy link
Contributor Author

gajus commented Apr 3, 2020

Thank you!

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.

4 participants