added information about how deprecations work #2246
Conversation
fabpot
commented
Feb 18, 2013
| Q | A |
|---|---|
| Doc fix? | no |
| New docs? | yes |
| Applies to | all |
| Fixed tickets | n/a |
| deprecated, the version when it will be removed, and whenever possible, how | ||
| the feature was replaced. | ||
|
|
||
| A PHP error must also be triggered to help people with the migration one or |
There was a problem hiding this comment.
IIUC "depending" and "must" are contradictory
maybe "[...] starting one or two[...]"
There was a problem hiding this comment.
A PHP E_USER_DEPRECATED error
|
git add ? |
| Deprecations | ||
| ------------ | ||
|
|
||
| From time to time, some classes and/or methods are deprecated in the |
There was a problem hiding this comment.
And think this should also be replaced with classes, methods, properties, constants, ect.?
There was a problem hiding this comment.
no, as you deprecate a feature that is implemented in classes/methods.
There was a problem hiding this comment.
I don't get why ie constants or interfaces would not be valid cases here also
There was a problem hiding this comment.
Because a feature cannot be made of constants only. You are nitpicking here.
There was a problem hiding this comment.
They are times when we only deprecate a constant / option (ie form).
I think interfaces are at least non disputable.
|
I think it is good to mention the |