Repository navigation
docs: specific warning suppression - #6871
Conversation
github-actions
Bot
added
the
documentation
jsumners
left a comment
jsumners
left a comment
There was a problem hiding this comment.
I can't remember if we intentionally kept the documentation here brief or not. I think the brevity forces people to read the upstream documentation and also imparts that we don't really think folks should be doing this.
That last point is what has me on the fence about this. The more we tell people how to turn off the warnings, the less likely they are to heed them. My inclination is to say we shouldn't point out this new flag at all and if someone figures out the possibility from their knowledge of core, so be it.
But the short text proposed is otherwise fine.
I think this is somewhat controversial, not a clear consensus on this:
Like you I am very defensive, but only as a default, users should have the liberty at the end of the day My concern is why the approved flag is still marked Stability: 1.1 Active development. cc @Ethan-Arrowood, any update on this? |
Little people interested in further development. I believe it just need volunteer to push the status. |
|
@jsumners I am pushing a doc update to Node core, I recommend we wait their answer. |
Co-authored-by: Manuel Spigolon <[email protected]> Signed-off-by: Jean Michelet <[email protected]>
Signed-off-by: Jean <[email protected]>
|
I removed the note because nodejs/node#64742 has been merged, so we can consider it stable. |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Curious that this is still on Stability 1.1 after many years?