You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading through parts of the http2 documentation, I'm missing information about what arguments are passed in many events. It's like documenting that there's a function called foo but not what argument it takes.
If an event is emitted without any arguments, writing "Emitted without any arguments" in the documentation would be helpful. I tend to console.log(arguments) just to see what's there, and this forces me to try to cause events to actually be emitted... I'm probably not the only one.
stream:aborted 😶 "Writable end". Is that my end, or the remote peers? Is abortion an error, i.e. should I expect an argument? stream:error 🤒 No argument in an error event. Or? Probably there is one... stream:frameError 🤔 Interesting... stream:streamClosed 🤗 Actually useful description, since it describes how this event relates to the flow of other events. stream:timeout 🙁 What, am I supposed to do? I read the doc for setTimeout and it seems I should manually perform things in this event handler... stream:trailers 😂 More flags! 🏳️🌈
I realize http2 is in early stage. But for early adopters and testers, this kind of information is very useful if it is provided. I've seen this lack of information before in other modules, so probably the documentation needs an overhaul of the events specifically, with exactly what is being sent.
@gireeshpunathil it would be fantastic if someone went through that list and opened issues (maybe with good-first-contribution label) for all of the events that are missing.
Looks like this got closed because of the Fixes tag in nodejs/node#30373
@dev-313 - can you pls confirm all the items that are listed in the checklist (#877 (comment)) are covered? If not, are you going to plan to work on those?
Looks like this got closed because of the Fixes tag in nodejs/node#30373
@dev-313 - can you pls confirm all the items that are listed in the checklist (#877 (comment)) are covered? If not, are you going to plan to work on those?
Final PR as referred in #877 (comment) would mean to go through the http2.md doc and making sure the doc text is consistent (wordings, construct, style etc.) and if not, make so. I don't think we need to hold up this issue for that; so will close this. If you find anything that needs change, please go ahead a raise a PR; or else, that is it!
Activity
gireeshpunathil commentedon Apr 2, 2018
@grantila - is this still outstanding? are you in a position to contribute to the improvement on the documentation?
gireeshpunathil commentedon Apr 12, 2018
Ping @nodejs/http2 to figure out next action here
mcollina commentedon Apr 12, 2018
@gireeshpunathil it would be fantastic if someone went through that list and opened issues (maybe with good-first-contribution label) for all of the events that are missing.
ryzokuken commentedon Apr 12, 2018
@mcollina I could try opening a few by this weekend.
mcollina commentedon Apr 12, 2018
awesome! Remember to tag @nodejs/http2 in all of them.
ryzokuken commentedon Apr 13, 2018
Checklist for reference
Http2Session
session:socketErrorHttp2Stream
Final
doc,http2: add parameters for Http2Session:connect event
doc: add parameters for Http2Session:error event
147 remaining items
doc: explain http2 aborted event callback
doc: improve doc Http2Stream: FrameError, Timeout and Trailers
gireeshpunathil commentedon Dec 10, 2019
Looks like this got closed because of the
Fixestag in nodejs/node#30373@dev-313 - can you pls confirm all the items that are listed in the checklist (#877 (comment)) are covered? If not, are you going to plan to work on those?
Keeping it open until then.
dev-script commentedon Dec 11, 2019
ok @gireeshpunathil
dev-script commentedon Dec 11, 2019
Checklist for remaining tasks
Http2Session
Http2Stream
stream:aborted
stream:error(Https2Stream 'error' event same as Https2Session so i think no need to change.)stream:frameError
stream:streamClosed(it might have been removed.)stream:timeout
stream:trailers
dev-script commentedon Dec 13, 2019
@gireeshpunathil All remaining tasks are completed but can you please help me to understand last task "Final PR".
gireeshpunathil commentedon Dec 13, 2019
thanks @dev-313 (and others) for doing this!
Final PRas referred in #877 (comment) would mean to go through thehttp2.mddoc and making sure the doc text is consistent (wordings, construct, style etc.) and if not, make so. I don't think we need to hold up this issue for that; so will close this. If you find anything that needs change, please go ahead a raise a PR; or else, that is it!thanks again!
dev-script commentedon Dec 14, 2019
Thanks @gireeshpunathil. If i find anything that need change, I'll raise a PR.
doc: improve doc Http2Stream: FrameError, Timeout and Trailers
doc: improve doc Http2Stream: FrameError, Timeout and Trailers
doc: improve doc Http2Stream: FrameError, Timeout and Trailers