Skip to content

Commit

Permalink
Update UPGRADE-5.1.md
Browse files Browse the repository at this point in the history
I guess there was a mistake on the Config upgrade. The method's name which signature has changed is `NodeDefinition::setDeprecated(...)` (instead of `NodeDefinition::setDeprecation(...)`).
Same thing goes for `BaseNode::setDeprecated(...).

Thanks :)
  • Loading branch information
MeroveeCharrue authored Sep 6, 2020
1 parent c98e160 commit 144599f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions UPGRADE-5.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@ UPGRADE FROM 5.0 to 5.1
Config
------

* The signature of method `NodeDefinition::setDeprecated()` has been updated to `NodeDefinition::setDeprecation(string $package, string $version, string $message)`.
* The signature of method `BaseNode::setDeprecated()` has been updated to `BaseNode::setDeprecation(string $package, string $version, string $message)`.
* The signature of method `NodeDefinition::setDeprecated()` has been updated to `NodeDefinition::setDeprecated(string $package, string $version, string $message)`.
* The signature of method `BaseNode::setDeprecated()` has been updated to `BaseNode::setDeprecated(string $package, string $version, string $message)`.
* Passing a null message to `BaseNode::setDeprecated()` to un-deprecate a node is deprecated
* Deprecated `BaseNode::getDeprecationMessage()`, use `BaseNode::getDeprecation()` instead

Expand Down

0 comments on commit 144599f

Please sign in to comment.