Completed
Push — master ( 689084...daf696 )
by Joao
10s
created

src/HandleOutput/JsonHandler.php (4 issues)

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

1
<?php
2
3
namespace ByJG\RestServer\HandleOutput;
4
5
use ByJG\RestServer\ServiceAbstract;
6
use ByJG\RestServer\Whoops\JsonResponseHandler;
7
use ByJG\Serializer\Formatter\JsonFormatter;
8
9 View Code Duplication
class JsonHandler implements HandleOutputInterface
0 ignored issues
show
This class seems to be duplicated in your project.

Duplicated code is one of the most pungent code smells. If you need to duplicate the same code in three or more different places, we strongly encourage you to look into extracting the code into a single class or operation.

You can also find more detailed suggestions in the “Code” section of your repository.

Loading history...
10
{
11
12
    public function writeHeader()
13
    {
14
        header('Content-Type: application/json');
15
        // header('Access-Control-Allow-Origin: *');
0 ignored issues
show
Unused Code Comprehensibility introduced by
67% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
16
        // header("Access-Control-Allow-Headers: X-API-KEY, Origin, X-Requested-With, Content-Type, Accept, Access-Control-Request-Method");
0 ignored issues
show
Unused Code Comprehensibility introduced by
67% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
17
        // header("Access-Control-Allow-Methods: GET, POST, OPTIONS, PUT, DELETE");
0 ignored issues
show
Unused Code Comprehensibility introduced by
67% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
18
    }
19
20
    public function writeOutput(ServiceAbstract $instance)
21
    {
22
        $serialized = $instance->getResponse()->getResponseBag()->process();
23
        return (new JsonFormatter())->process($serialized);
24
    }
25
26
    public function getErrorHandler()
27
    {
28
        return new JsonResponseHandler();
29
    }
30
}
31