Packages: Deprecated: Gutenberg-independent deprecations #9753
Labels
Needs Decision
Needs a decision to be actionable or relevant
[Package] Deprecated
packages/deprecated
[Type] Breaking Change
For PRs that introduce a change that will break existing functionality
[Type] Enhancement
A suggestion for improvement.
Related: Discussed during September 4th JavaScript Chat
Currently, all calls to the
deprecated
function pass a Gutenberg version number at which the feature is to be deprecated. This is sensible within the context of the Gutenberg plugin, but has no meaning in the context of the published npm package.This raises a few questions (action items denoted by⚠️ ):
deprecated
message is published (reference).deprecated
module messaging. The Gutenberg references should be added by an extension via [???] (implementation undetermined)deprecated
includeplugin
andversion
options?plugin
option is probably unnecessary, though it may be sensible to have some built-in knowledge / messaging of a deprecation removal version. In these cases, it may be required to allow granular extension of specific message fragments (e.g. the variables composing thedeprecated
message).The text was updated successfully, but these errors were encountered: