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
The description of the Deprecatedstability index in fact contradicts with the recent decision about the old Buffer API. It is currently deprecated in a sense that a complete drop-in replacement exists and that the old API usage is highly discouraged, but we recently decided on a CTC vote that we do not plan any changes there at this point. The description in the documentation directly contradicts that.
Current description:
Deprecated: This feature is known to be problematic, and changes are planned. Do not rely on it. Use of the feature may cause warnings. Backwards compatibility should not be expected.
The same question affects domain — it's labelled as Deprecated, but can we say now that we have plans actually removing/changing that? Related: #10843.
The text was updated successfully, but these errors were encountered:
ChALkeR
changed the title
doc: the «Deprecated» stability index is inaccurate
doc: the «Deprecated» stability index description is inaccurate
May 4, 2017
IMHO simplest solution is to explicitly state the status of these two modules in a note at the end of the definition...
meta-deprecation of the deprecation definition... 😲
Previous discussion at #12723 (comment).
The description of the
Deprecated
stability index in fact contradicts with the recent decision about the old Buffer API. It is currently deprecated in a sense that a complete drop-in replacement exists and that the old API usage is highly discouraged, but we recently decided on a CTC vote that we do not plan any changes there at this point. The description in the documentation directly contradicts that.Current description:
The same question affects
domain
— it's labelled asDeprecated
, but can we say now that we have plans actually removing/changing that? Related: #10843./cc @jasnell @addaleax @Trott @MylesBorins
The text was updated successfully, but these errors were encountered: