| Conditions | 6 |
| Paths | 19 |
| Total Lines | 60 |
| Code Lines | 24 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 0 | ||
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | <?php |
||
| 88 | $view->summaryBasket = $basket; |
||
| 89 | $view->confirmOrderItem = \Aimeos\Controller\Frontend::create( $context, 'order' )->get( $id, false ); |
||
| 90 | |||
| 91 | |||
| 92 | return parent::data( $view, $tags, $expire ); |
||
| 93 | } |
||
| 94 | |||
| 95 | |||
| 96 | /** client/html/checkout/confirm/template-body |
||
| 97 | * Relative path to the HTML body template of the checkout confirm client. |
||
| 98 | * |
||
| 99 | * The template file contains the HTML code and processing instructions |
||
| 100 | * to generate the result shown in the body of the frontend. The |
||
| 101 | * configuration string is the path to the template file relative |
||
| 102 | * to the templates directory (usually in client/html/templates). |
||
| 103 | * |
||
| 104 | * You can overwrite the template file configuration in extensions and |
||
| 105 | * provide alternative templates. These alternative templates should be |
||
| 106 | * named like the default one but suffixed by |
||
| 107 | * an unique name. You may use the name of your project for this. If |
||
| 108 | * you've implemented an alternative client class as well, it |
||
| 109 | * should be suffixed by the name of the new class. |
||
| 110 | * |
||
| 111 | * @param string Relative path to the template creating code for the HTML page body |
||
| 112 | * @since 2014.03 |
||
| 113 | * @see client/html/checkout/confirm/template-header |
||
| 114 | */ |
||
| 115 | |||
| 116 | /** client/html/checkout/confirm/template-header |
||
| 117 | * Relative path to the HTML header template of the checkout confirm client. |
||
| 118 | * |
||
| 119 | * The template file contains the HTML code and processing instructions |
||
| 120 | * to generate the HTML code that is inserted into the HTML page header |
||
| 121 | * of the rendered page in the frontend. The configuration string is the |
||
| 122 | * path to the template file relative to the templates directory (usually |
||
| 123 | * in client/html/templates). |
||
| 124 | * |
||
| 125 | * You can overwrite the template file configuration in extensions and |
||
| 126 | * provide alternative templates. These alternative templates should be |
||
| 127 | * named like the default one but suffixed by |
||
| 128 | * an unique name. You may use the name of your project for this. If |
||
| 129 | * you've implemented an alternative client class as well, it |
||
| 130 | * should be suffixed by the name of the new class. |
||
| 131 | * |
||
| 132 | * @param string Relative path to the template creating code for the HTML page head |
||
| 133 | * @since 2014.03 |
||
| 134 | * @see client/html/checkout/confirm/template-body |
||
| 135 | */ |
||
| 136 | } |
||
| 137 |