| Conditions | 2 |
| Paths | 2 |
| Total Lines | 12 |
| Code Lines | 7 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
| 1 | <?php |
||
| 42 | protected function getDefaultOperations(EntityInterface $entity) { |
||
| 43 | $operations = parent::getDefaultOperations($entity); |
||
| 44 | |||
| 45 | // Destination parameter messes up with the entity form wizard redirects. |
||
| 46 | $options = $operations['edit']['url']->getOptions(); |
||
| 47 | if (!empty($options['query']['destination'])) { |
||
| 48 | unset($options['query']['destination']); |
||
| 49 | } |
||
| 50 | $operations['edit']['url']->setOptions($options); |
||
| 51 | |||
| 52 | return $operations; |
||
| 53 | } |
||
| 54 | |||
| 56 |
Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code.
Let’s take a look at an example:
As you can see in this example, the array
$myArrayis initialized the first time when the foreach loop is entered. You can also see that the value of thebarkey is only written conditionally; thus, its value might result from a previous iteration.This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization $myArray = array() either outside or inside the foreach loop.