YetiForceCompany/YetiForceCRM

View on GitHub
modules/Settings/Magento/views/Edit.php

Summary

Maintainability
A
3 hrs
Test Coverage
F
0%

Missing class import via use statement (line '25', column '23').
Open

            throw new \App\Exceptions\NoPermittedForAdmin('LBL_PERMISSION_DENIED');

MissingImport

Since: 2.7.0

Importing all external classes in a file through use statements makes them clearly visible.

Example

function make() {
    return new \stdClass();
}

Source http://phpmd.org/rules/cleancode.html#MissingImport

The method process uses an else expression. Else clauses are basically not necessary and you can simplify the code by not using them.
Open

        } else {
            $recordModel = Settings_Magento_Record_Model::getCleanInstance();
        }

ElseExpression

Since: 1.4.0

An if expression with an else branch is basically not necessary. You can rewrite the conditions in a way that the else clause is not necessary and the code becomes simpler to read. To achieve this, use early return statements, though you may need to split the code it several smaller methods. For very simple assignments you could also use the ternary operations.

Example

class Foo
{
    public function bar($flag)
    {
        if ($flag) {
            // one branch
        } else {
            // another branch
        }
    }
}

Source https://phpmd.org/rules/cleancode.html#elseexpression

Avoid using static access to class '\App\YetiForce\Register' in method 'checkPermission'.
Open

        if(!\App\YetiForce\Register::getProduct('YetiForceMagento')) {

StaticAccess

Since: 1.4.0

Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

Example

class Foo
{
    public function bar()
    {
        Bar::baz();
    }
}

Source https://phpmd.org/rules/cleancode.html#staticaccess

Avoid using static access to class 'Settings_Magento_Record_Model' in method 'process'.
Open

            $recordModel = Settings_Magento_Record_Model::getCleanInstance();

StaticAccess

Since: 1.4.0

Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

Example

class Foo
{
    public function bar()
    {
        Bar::baz();
    }
}

Source https://phpmd.org/rules/cleancode.html#staticaccess

Avoid using static access to class 'Settings_Magento_Record_Model' in method 'process'.
Open

            $recordModel = Settings_Magento_Record_Model::getInstanceById($record);

StaticAccess

Since: 1.4.0

Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

Example

class Foo
{
    public function bar()
    {
        Bar::baz();
    }
}

Source https://phpmd.org/rules/cleancode.html#staticaccess

Call to undeclared method \Vtiger_Viewer::assign
Open

        $viewer->assign('RECORD_MODEL', $recordModel);
Severity: Critical
Found in modules/Settings/Magento/views/Edit.php by phan

Call to undeclared method \Vtiger_Viewer::assign
Open

        $viewer->assign('QUALIFIED_MODULE', $moduleName);
Severity: Critical
Found in modules/Settings/Magento/views/Edit.php by phan

Call to method getProduct from undeclared class \App\YetiForce\Register
Open

        if(!\App\YetiForce\Register::getProduct('YetiForceMagento')) {
Severity: Critical
Found in modules/Settings/Magento/views/Edit.php by phan

Call to undeclared method \Vtiger_Viewer::assign
Open

        $viewer->assign('RECORD_ID', $record);
Severity: Critical
Found in modules/Settings/Magento/views/Edit.php by phan

Identical blocks of code found in 2 locations. Consider refactoring.
Open

    public function process(App\Request $request)
    {
        $moduleName = $request->getModule(false);
        $viewer = $this->getViewer($request);
        $record = !$request->isEmpty('record') ? $request->getInteger('record') : '';
Severity: Major
Found in modules/Settings/Magento/views/Edit.php and 1 other location - About 3 hrs to fix
modules/Settings/MailSmtp/views/Edit.php on lines 18..32

Duplicated Code

Duplicated code can lead to software that is hard to understand and difficult to change. The Don't Repeat Yourself (DRY) principle states:

Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

When you violate DRY, bugs and maintenance problems are sure to follow. Duplicated code has a tendency to both continue to replicate and also to diverge (leaving bugs as two similar implementations differ in subtle ways).

Tuning

This issue has a mass of 148.

We set useful threshold defaults for the languages we support but you may want to adjust these settings based on your project guidelines.

The threshold configuration represents the minimum mass a code block must have to be analyzed for duplication. The lower the threshold, the more fine-grained the comparison.

If the engine is too easily reporting duplication, try raising the threshold. If you suspect that the engine isn't catching enough duplication, try lowering the threshold. The best setting tends to differ from language to language.

See codeclimate-duplication's documentation for more information about tuning the mass threshold in your .codeclimate.yml.

Refactorings

Further Reading

Each class must be in a namespace of at least one level (a top-level vendor name)
Open

class Settings_Magento_Edit_View extends Settings_Vtiger_Index_View

The class Settings_Magento_Edit_View is not named in CamelCase.
Open

class Settings_Magento_Edit_View extends Settings_Vtiger_Index_View
{
    /** {@inheritdoc} */
    public function checkPermission(Request $request)
    {

CamelCaseClassName

Since: 0.2

It is considered best practice to use the CamelCase notation to name classes.

Example

class class_name {
}

Source

Expected 1 space after IF keyword; 0 found
Open

        if(!\App\YetiForce\Register::getProduct('YetiForceMagento')) {

Class name "Settings_Magento_Edit_View" is not in camel caps format
Open

class Settings_Magento_Edit_View extends Settings_Vtiger_Index_View

There are no issues that match your filters.

Category
Status