Issues in TestCase.php - Fixed Issues - Inspection of "Upgrade to Laravel 5.5" - jumilla/laravel-addomnipot - Measure and Improve Code Quality continuously with Scrutinizer

Completed

by Fumio

created 2017-09-19 10:56 UTC

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

<?php

abstract class TestCase extends PHPUnit_Framework_TestCase
namespace YourVendor;

class YourClass { }
{
}


1			<?php
2
3			abstract class TestCase extends PHPUnit_Framework_TestCase
			0 ignored issues – show Comprehensibility Best Practice introduced 2016-08-26 12:46 UTC by Report Bug Copy Issue Report Show Similar Issues like this The type `TestCase` has been defined more than once; this definition is ignored, only the first definition in `stubs/api/TestCase.php` (L3-5) is considered. This check looks for classes that have been defined more than once. If you can, we would recommend to use standard object-oriented programming techniques. For example, to avoid multiple types, it might make sense to create a common interface, and then multiple, different implementations for that interface. This also has the side-effect of providing you with better IDE auto-completion, static analysis and also better OPCode caching from PHP. Loading history... Coding Style Compatibility introduced 2016-08-26 12:46 UTC by Report Bug Copy Issue Report Show Similar Issues like this 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...
4			{
5			}
6

jumilla / laravel-addomnipot