superdesk /
web-publisher
| Conditions | 3 |
| Paths | 1 |
| Total Lines | 57 |
| 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 |
||
| 130 | public function searchAction(Request $request) |
||
| 131 | { |
||
| 132 | $currentTenant = $this->get('swp_multi_tenancy.tenant_context')->getTenant(); |
||
| 133 | |||
| 134 | $criteria = Criteria::fromQueryParameters( |
||
| 135 | $request->query->get('term', ''), |
||
| 136 | [ |
||
| 137 | 'page' => $request->query->get('page'), |
||
| 138 | 'sort' => $request->query->get('sorting'), |
||
| 139 | 'limit' => $request->query->get('limit', 10), |
||
| 140 | 'routes' => array_filter((array) $request->query->get('route', [])), |
||
| 141 | 'statuses' => array_filter((array) $request->query->get('status', [])), |
||
| 142 | 'authors' => array_filter((array) $request->query->get('author', [])), |
||
| 143 | 'publishedBefore' => $request->query->has('published_before') ? new \DateTime($request->query->get('published_before')) : null, |
||
| 144 | 'publishedAfter' => $request->query->has('published_after') ? new \DateTime($request->query->get('published_after')) : null, |
||
| 145 | 'publishedAt' => $request->query->get('published_at'), |
||
| 146 | 'tenantCode' => $currentTenant->getCode(), |
||
| 147 | 'sources' => array_filter((array) $request->query->get('source', [])), |
||
| 148 | 'metadata' => array_filter((array) $request->query->get('metadata', [])), |
||
| 149 | ] |
||
| 150 | ); |
||
| 151 | |||
| 152 | $extraFields = $this->get('service_container')->getParameter('env(ELASTICA_ARTICLE_EXTRA_FIELDS)'); |
||
| 153 | |||
| 154 | $options = [ |
||
| 155 | 'sortNestedPath' => 'articleStatistics.pageViewsNumber', |
||
| 156 | ]; |
||
| 157 | |||
| 158 | $repositoryManager = $this->get('fos_elastica.manager'); |
||
| 159 | /** @var ArticleRepository $repository */ |
||
| 160 | $repository = $repositoryManager->getRepository($this->getParameter('swp.model.article.class')); |
||
| 161 | $articles = $repository->findByCriteria($criteria, json_decode($extraFields, true)); |
||
| 162 | $paginator = $this->get('knp_paginator'); |
||
| 163 | $pagination = $paginator->paginate( |
||
| 164 | $articles, |
||
| 165 | $request->query->get('page', 1), |
||
| 166 | $criteria->getPagination()->getItemsPerPage(), |
||
| 167 | $options |
||
| 168 | ); |
||
| 169 | |||
| 170 | $responseContext = new ResponseContext(); |
||
| 171 | $responseContext->setSerializationGroups( |
||
| 172 | [ |
||
| 173 | 'Default', |
||
| 174 | 'api_articles_list', |
||
| 175 | 'api_articles_featuremedia', |
||
| 176 | 'api_article_media_list', |
||
| 177 | 'api_article_media_renditions', |
||
| 178 | 'api_image_details', |
||
| 179 | 'api_routes_list', |
||
| 180 | 'api_tenant_list', |
||
| 181 | 'api_articles_statistics_list', |
||
| 182 | ] |
||
| 183 | ); |
||
| 184 | |||
| 185 | return new ResourcesListResponse($pagination, $responseContext); |
||
| 186 | } |
||
| 187 | } |
||
| 188 |
This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message.
The explanatory message should give you some clue as to whether and when the type will be removed from the class and what other constant to use instead.