-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Deprecated: Output an informational message for deprecation when no version provided #16774
Conversation
@aduth, should we add gutenberg/packages/e2e-tests/config/setup-test-framework.js Lines 32 to 35 in 32b7b34
We already cover it for unit tests through gutenberg/packages/jest-console/src/supported-matchers.js Lines 1 to 6 in 32b7b34
|
Hm, I like the updated string, but I feel like we should always warn when something is deprecated. It shouldn't be interpreted as advisory, it should be a motivator to move away from. |
I tend to agree with @aduth that deprecations should be a warning indifferent of version. It is one of the ways that pushes people to work on stuff they don't like, all these warnings, while informational messages are not motivating enough :) Something to add is the word "version" to this string: "%feature% is deprecated and will be removed in version 11" |
…ersion provided When there is no `options.version` param provided `deprecated` method outputs an informational message to the Web Console rather than warns as previously.
2d304fc
to
87859a9
Compare
87859a9
to
1a7630a
Compare
@aduth and @draganescu - I changed back to |
…round version param
Deprecated enhancements got me thinking: #16842 |
Yeah, very cool ideas 💯 |
…ersion provided (#16774) * Deprecated: Output an informational message for deprecation when no version provided When there is no `options.version` param provided `deprecated` method outputs an informational message to the Web Console rather than warns as previously. * Use warn for all deprecations * Update unit tests for deprecated method to make them less confusing around version param
…ersion provided (#16774) * Deprecated: Output an informational message for deprecation when no version provided When there is no `options.version` param provided `deprecated` method outputs an informational message to the Web Console rather than warns as previously. * Use warn for all deprecations * Update unit tests for deprecated method to make them less confusing around version param
Description
When there is no
options.version
param provideddeprecated
method outputs more relaxed warning message to the Web Console.The fact that we warn when there is no clear path for removing deprecation is very confusing in my opinion. The change proposed tries to make it less dramatic for 3rd party developers. The idea is that when there is no version provided we are going to support deprecated version forever according to Deprecations document. As soon as we decide to remove it, we should specify the target version for removal and it will automatically make the message stronger.
Before
After