Skip to content

[Insight] Missing use statement should be avoided - in Controller/BackendController.php, line 56 #106

@gonzaloalonsod

Description

@gonzaloalonsod

in Controller/BackendController.php, line 56

The Exception class resolves to the following classes: Imagine\Exception\Exception or Symfony\Component\Config\Definition\Exception\Exception or Ivory\CKEditorBundle\Exception\Exception.
Did you forget to add a corresponding use statement for one of them?

                        $entity->$fieldname_set(true);
                    }

                    $em->flush();
                    $res = true;
                } catch (Exception $e) {}
            }
        }

        $response = new JsonResponse();
        $response->setData($res);

Posted from SensioLabsInsight

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions