ForSaleOnePage::getCMSFields() - Code Metrics - sunnysideup/silverstripe-forsale - Measure and Improve Code Quality continuously with Scrutinizer

ForSaleOnePage::getCMSFields() A
last analyzed 2018-03-20 01:15 UTC

↳ Parent: ForSaleOnePage

Complexity

Conditions	1
Paths	1

Size

Total Lines	12
Code Lines	10

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
dl	0
loc	12
rs	9.4285
c	0
b	0
f	0
cc	1
eloc	10
nc	1
nop	0

<?php
/**
 *@author nicolaas[at] sunnysideup.co.nz
 *@description: individual ForSale page. Usually, these are not viewed as they can be read completely from the parent (ForSale HOLDER) page.
 */
class ForSaleOnePage extends Page
namespace YourVendor;

class YourClass { }
{
    public static $icon = "mysite/images/treeicons/ForSaleOnePage";

    public static $default_parent = 'ForSaleHolderPage';

    public static $allowed_children = "none";

    public static $db = array(
        "IntroText" => "Varchar(255)",
        "PriceDescription" => "Varchar(255)",
        "ContactDetails" => "HTMLText"
    );

    public static $has_one = array(
        "ProductImage" => "Image"
    );


    //static $has_many = array();


    public function getCMSFields()

    {
        $fields = parent::getCMSFields();
        $fields->replaceField("Title", new TextField("Title", "Product Name"));
        $fields->replaceField("MenuTitle", new TextField("MenuTitle", "Product Name - short version for menus"));
        $fields->replaceField("Content", new HtmlEditorField("Content", "Product Description", $rows = 7, $cols = 7));
        $fields->addFieldToTab("Root.Content.ProductInfo", new TextField("IntroText", "Intro Text"));
        $fields->addFieldToTab("Root.Content.ProductInfo", new TextField("PriceDescription", "Price Description"));
        $fields->addFieldToTab("Root.Content.ProductInfo", new HtmlEditorField("ContactDetails", "Contact Details", $rows = 7, $cols = 7));
        $fields->addFieldToTab("Root.Content.ProductInfo", new ImageField("ProductImage", "Product Image"));
        return $fields;
    }
}

class ForSaleOnePage_Controller extends Page_Controller
namespace YourVendor;

class YourClass { }
{
    public function init()
    {
        parent::init();
    }
}


1			<?php
2			/**
3			*@author nicolaas[at] sunnysideup.co.nz
4			*@description: individual ForSale page. Usually, these are not viewed as they can be read completely from the parent (ForSale HOLDER) page.
5			*/
6			class ForSaleOnePage extends Page
			0 ignored issues – show Coding Style Compatibility introduced 2017-01-03 01:17 UTC by Report Bug Copy Issue Report PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions. You can fix this by adding a namespace to your class: namespace YourVendor; class YourClass { } When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries. Loading history...
7			{
8			public static $icon = "mysite/images/treeicons/ForSaleOnePage";
9
10			public static $default_parent = 'ForSaleHolderPage';
11
12			public static $allowed_children = "none";
13
14			public static $db = array(
15			"IntroText" => "Varchar(255)",
16			"PriceDescription" => "Varchar(255)",
17			"ContactDetails" => "HTMLText"
18			);
19
20			public static $has_one = array(
21			"ProductImage" => "Image"
22			);
23
24
25			//static $has_many = array();
			0 ignored issues – show Unused Code Comprehensibility introduced 2017-01-03 01:17 UTC by Report Bug Copy Issue Report `60%` 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...
26
27			public function getCMSFields()
			0 ignored issues – show Documentation introduced 2018-02-21 04:03 UTC by Report Bug Copy Issue Report The return type could not be reliably inferred; please add a `@return` annotation. Our type inference engine in quite powerful, but sometimes the code does not provide enough clues to go by. In these cases we request you to add a `@return` annotation as described here. Loading history...
28			{
29			$fields = parent::getCMSFields();
30			$fields->replaceField("Title", new TextField("Title", "Product Name"));
31			$fields->replaceField("MenuTitle", new TextField("MenuTitle", "Product Name - short version for menus"));
32			$fields->replaceField("Content", new HtmlEditorField("Content", "Product Description", $rows = 7, $cols = 7));
33			$fields->addFieldToTab("Root.Content.ProductInfo", new TextField("IntroText", "Intro Text"));
34			$fields->addFieldToTab("Root.Content.ProductInfo", new TextField("PriceDescription", "Price Description"));
35			$fields->addFieldToTab("Root.Content.ProductInfo", new HtmlEditorField("ContactDetails", "Contact Details", $rows = 7, $cols = 7));
36			$fields->addFieldToTab("Root.Content.ProductInfo", new ImageField("ProductImage", "Product Image"));
37			return $fields;
38			}
39			}
40
41			class ForSaleOnePage_Controller extends Page_Controller
			0 ignored issues – show Coding Style Compatibility introduced 2017-01-03 01:17 UTC by Report Bug Copy Issue Report PSR1 recommends that each class should be in its own file to aid autoloaders. Having each class in a dedicated file usually plays nice with PSR autoloaders and is therefore a well established practice. If you use other autoloaders, you might not want to follow this rule. Loading history... Coding Style Compatibility introduced 2017-01-03 01:17 UTC by Report Bug Copy Issue Report PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions. You can fix this by adding a namespace to your class: namespace YourVendor; class YourClass { } When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries. Loading history...
42			{
43			public function init()
44			{
45			parent::init();
46			}
47			}
48

sunnysideup / silverstripe-forsale

ForSaleOnePage::getCMSFields() A last analyzed 2018-03-20 01:15 UTC

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like

ForSaleOnePage::getCMSFields() A
last analyzed 2018-03-20 01:15 UTC