FieldRendererOutlineBox::render() - Code Metrics - Inspection of "Move FieldParser construction burden to FieldParse..." - graze/ciff-renderer - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Pull Request — refactor-01-decoupling (#27)

by John

created 2017-03-11 09:36 UTC

FieldRendererOutlineBox::render() A

↳ Parent: FieldRendererOutlineBox

Complexity

Conditions	1
Paths	1

Size

Total Lines	21
Code Lines	15

Duplication

Lines	0
Ratio	0 %

Code Coverage

Tests	0
CRAP Score	2

Importance

Changes

Metric	Value
dl	0
loc	21
ccs	0
cts	19
cp	0
rs	9.3142
c	0
b	0
f	0
cc	1
eloc	15
nc	1
nop	4
crap	2

<?php

namespace Graze\CiffRenderer\Renderer\FieldRenderer;

use Graze\CiffRenderer\Renderer\FieldRenderer\FieldRendererInterface;
use Intervention\Image\ImageManager;
use Graze\CiffRenderer\Parser\FieldParser\FieldParserInterface;

class FieldRendererOutlineBox implements FieldRendererInterface
{
    /**
     * @param ImageManager $imageManager
     * @param FieldParserInterface $parser
     * @param callable $fontResolver

     * @param callable $graphicResolver

     * @return Intervention\Image\Image

     */
    public function render(
        ImageManager $imageManager,
        FieldParserInterface $parser,
        callable $fontResolver = null,
        callable $graphicResolver = null
    ) {
        $image = $imageManager->canvas($parser->getWidth(), $parser->getHeight());

        $rectangleConf = function ($rectangle) use ($parser) {
            $rectangle->border($parser->getLineWeight(), '#000');
        };
        $image->rectangle(
            0,
            0,
            $parser->getWidth() - $parser->getLineWeight(),
            $parser->getHeight() - $parser->getLineWeight(),
            $rectangleConf
        );

        return $image;
class Author {
    private $name;

    public function __construct($name) {
        $this->name = $name;
    }

    public function getName() {
        return $this->name;
    }
}

abstract class Post {
    public function getAuthor() {
        return 'Johannes';
    }
}

class BlogPost extends Post {
    public function getAuthor() {
        return new Author('Johannes');
    }
}

class ForumPost extends Post { /* ... */ }

function my_function(Post $post) {
    echo strtoupper($post->getAuthor());
}
    }

    /**
     * @return FieldRendererInterface
     */
    public static function factory()
    {
        return new static();
class Author {
    private $name;

    public function __construct($name) {
        $this->name = $name;
    }

    public function getName() {
        return $this->name;
    }
}

abstract class Post {
    public function getAuthor() {
        return 'Johannes';
    }
}

class BlogPost extends Post {
    public function getAuthor() {
        return new Author('Johannes');
    }
}

class ForumPost extends Post { /* ... */ }

function my_function(Post $post) {
    echo strtoupper($post->getAuthor());
}
    }
}


1			<?php
2
3			namespace Graze\CiffRenderer\Renderer\FieldRenderer;
4
5			use Graze\CiffRenderer\Renderer\FieldRenderer\FieldRendererInterface;
6			use Intervention\Image\ImageManager;
7			use Graze\CiffRenderer\Parser\FieldParser\FieldParserInterface;
8
9			class FieldRendererOutlineBox implements FieldRendererInterface
10			{
11			/**
12			* @param ImageManager $imageManager
13			* @param FieldParserInterface $parser
14			* @param callable $fontResolver
			0 ignored issues – show Documentation introduced 2016-11-22 22:36 UTC by Report Bug Copy Issue Report Should the type for parameter `$fontResolver` not be `null\|callable`? This check looks for `@param` annotations where the type inferred by our type inference engine differs from the declared type. It makes a suggestion as to what type it considers more descriptive. Most often this is a case of a parameter that can be null in addition to its declared types. Loading history...
15			* @param callable $graphicResolver
			0 ignored issues – show Documentation introduced 2016-11-22 22:36 UTC by Report Bug Copy Issue Report Should the type for parameter `$graphicResolver` not be `null\|callable`? This check looks for `@param` annotations where the type inferred by our type inference engine differs from the declared type. It makes a suggestion as to what type it considers more descriptive. Most often this is a case of a parameter that can be null in addition to its declared types. Loading history...
16			* @return Intervention\Image\Image
			0 ignored issues – show Documentation introduced 2016-11-22 22:36 UTC by Report Bug Copy Issue Report Should the return type not be `\Intervention\Image\Image`? This check compares the return type specified in the `@return` annotation of a function or method doc comment with the types returned by the function and raises an issue if they mismatch. Loading history...
17			*/
18			public function render(
19			ImageManager $imageManager,
20			FieldParserInterface $parser,
21			callable $fontResolver = null,
22			callable $graphicResolver = null
23			) {
24			$image = $imageManager->canvas($parser->getWidth(), $parser->getHeight());
25
26			$rectangleConf = function ($rectangle) use ($parser) {
27			$rectangle->border($parser->getLineWeight(), '#000');
28			};
29			$image->rectangle(
30			0,
31			0,
32			$parser->getWidth() - $parser->getLineWeight(),
33			$parser->getHeight() - $parser->getLineWeight(),
34			$rectangleConf
35			);
36
37			return $image;
			0 ignored issues – show Bug Best Practice introduced 2016-11-22 22:36 UTC by Report Bug Copy Issue Report The return type of `return $image;` (`Intervention\Image\Image`) is incompatible with the return type declared by the interface `Graze\CiffRenderer\Rende...ndererInterface::render` of type `Graze\CiffRenderer\Rende...ntervention\Image\Image`. If you return a value from a function or method, it should be a sub-type of the type that is given by the parent type f.e. an interface, or abstract method. This is more formally defined by the Lizkov substitution principle, and guarantees that classes that depend on the parent type can use any instance of a child type interchangably. This principle also belongs to the SOLID principles for object oriented design. Let’s take a look at an example: class Author { private $name; public function __construct($name) { $this->name = $name; } public function getName() { return $this->name; } } abstract class Post { public function getAuthor() { return 'Johannes'; } } class BlogPost extends Post { public function getAuthor() { return new Author('Johannes'); } } class ForumPost extends Post { /* ... */ } function my_function(Post $post) { echo strtoupper($post->getAuthor()); } Our function `my_function` expects a `Post` object, and outputs the author of the post. The base class `Post` returns a simple string and outputting a simple string will work just fine. However, the child class `BlogPost` which is a sub-type of `Post` instead decided to return an `object`, and is therefore violating the SOLID principles. If a `BlogPost` were passed to `my_function`, PHP would not complain, but ultimately fail when executing the `strtoupper` call in its body. Loading history...
38			}
39
40			/**
41			* @return FieldRendererInterface
42			*/
43			public static function factory()
44			{
45			return new static();
			0 ignored issues – show Bug Best Practice introduced 2016-11-22 22:36 UTC by Report Bug Copy Issue Report The return type of `return new static();` (`Graze\CiffRenderer\Rende...FieldRendererOutlineBox`) is incompatible with the return type declared by the interface `Graze\CiffRenderer\Rende...dererInterface::factory` of type `Graze\CiffRenderer\Parse...er\FieldParserInterface`. If you return a value from a function or method, it should be a sub-type of the type that is given by the parent type f.e. an interface, or abstract method. This is more formally defined by the Lizkov substitution principle, and guarantees that classes that depend on the parent type can use any instance of a child type interchangably. This principle also belongs to the SOLID principles for object oriented design. Let’s take a look at an example: class Author { private $name; public function __construct($name) { $this->name = $name; } public function getName() { return $this->name; } } abstract class Post { public function getAuthor() { return 'Johannes'; } } class BlogPost extends Post { public function getAuthor() { return new Author('Johannes'); } } class ForumPost extends Post { /* ... */ } function my_function(Post $post) { echo strtoupper($post->getAuthor()); } Our function `my_function` expects a `Post` object, and outputs the author of the post. The base class `Post` returns a simple string and outputting a simple string will work just fine. However, the child class `BlogPost` which is a sub-type of `Post` instead decided to return an `object`, and is therefore violating the SOLID principles. If a `BlogPost` were passed to `my_function`, PHP would not complain, but ultimately fail when executing the `strtoupper` call in its body. Loading history...
46			}
47			}
48

graze / ciff-renderer

Pull Request — refactor-01-decoupling (#27)

FieldRendererOutlineBox::render() A

Complexity

Size

Duplication

Code Coverage

Importance

Duplication Side-by-Side

Filter issues like