View GitHub Repository bpost-api-library

Schedule Inspection
Subscribe

AtBpost
last analyzed

↳ Parent: Project

Complexity

Total Complexity 0

Size/Duplication

Total Lines 1
Duplicated Lines 0 %

Coupling/Cohesion

Components 0
Dependencies 1

Importance

Changes 18
Bugs 3 Features 9
Metric Value
wmc 0
c 18
b 3
f 9
lcom 0
cbo 1
dl 0
loc 1
1 
<?php
2 
namespace TijsVerkoyen\Bpost { /** @deprecated */ class Bpack247 extends \Bpost\BpostApiClient\Bpack247 {} } // src/Bpack247.php
3 
namespace TijsVerkoyen\Bpost\Bpack247 { /** @deprecated */ class Customer extends \Bpost\BpostApiClient\Bpack247\Customer {} } // src/Bpack247/Customer.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
4 
namespace TijsVerkoyen\Bpost\Bpack247 { /** @deprecated */ class CustomerPackStation extends \Bpost\BpostApiClient\Bpack247\CustomerPackStation {} } // src/Bpack247/CustomerPackStation.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
5 
namespace TijsVerkoyen\Bpost { /** @deprecated */ class Bpost extends \Bpost\BpostApiClient\Bpost {} } // src/Bpost.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
6 
namespace TijsVerkoyen\Bpost\Bpost { /** @deprecated */ class Label extends \Bpost\BpostApiClient\Bpost\Label {} } // src/Bpost/Label.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
7 
namespace TijsVerkoyen\Bpost\Bpost { /** @deprecated */ class Order extends \Bpost\BpostApiClient\Bpost\Order {} } // src/Bpost/Order.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
8 
namespace TijsVerkoyen\Bpost\Bpost\Order { /** @deprecated */ class Address extends \Bpost\BpostApiClient\Bpost\Order\Address {} } // src/Bpost/Order/Address.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
9 
namespace TijsVerkoyen\Bpost\Bpost\Order { /** @deprecated */ class Box extends \Bpost\BpostApiClient\Bpost\Order\Box {} } // src/Bpost/Order/Box.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
10 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box { /** @deprecated */ class At247 extends \Bpost\BpostApiClient\Bpost\Order\Box\At247 {} } // src/Bpost/Order/Box/At247.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
11 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box { /** @deprecated */ class AtBpost extends \Bpost\BpostApiClient\Bpost\Order\Box\AtBpost {} } // src/Bpost/Order/Box/AtBpost.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
12 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box { /** @deprecated */ class AtHome extends \Bpost\BpostApiClient\Bpost\Order\Box\AtHome {} } // src/Bpost/Order/Box/AtHome.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
13 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box\Customsinfo { /** @deprecated */ class CustomsInfo extends \Bpost\BpostApiClient\Bpost\Order\Box\CustomsInfo\CustomsInfo {} } // src/Bpost/Order/Box/Customsinfo/CustomsInfo.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
14 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box { interface IBox extends \Bpost\BpostApiClient\Bpost\Order\Box\IBox {} } // src/Bpost/Order/Box/IBox.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
15 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box { /** @deprecated */ class International extends \Bpost\BpostApiClient\Bpost\Order\Box\International {} } // src/Bpost/Order/Box/International.php
0 ignored issues
– show
Coding Style Compatibility introduced by
Each interface must be in a file by itself

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...
16 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box { abstract class National extends \Bpost\BpostApiClient\Bpost\Order\Box\National {} } // src/Bpost/Order/Box/National.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
17 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box\Openinghour { /** @deprecated */ class Day extends \Bpost\BpostApiClient\Bpost\Order\Box\OpeningHour\Day {} } // src/Bpost/Order/Box/OpeningHour/Day.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
18 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box\Option { /** @deprecated */ class AutomaticSecondPresentation extends \Bpost\BpostApiClient\Bpost\Order\Box\Option\AutomaticSecondPresentation {} } // src/Bpost/Order/Box/Option/AutomaticSecondPresentation.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
19 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box\Option { /** @deprecated */ class CashOnDelivery extends \Bpost\BpostApiClient\Bpost\Order\Box\Option\CashOnDelivery {} } // src/Bpost/Order/Box/Option/CashOnDelivery.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
20 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box\Option { /** @deprecated */ class Insurance extends \Bpost\BpostApiClient\Bpost\Order\Box\Option\Insurance {} } // src/Bpost/Order/Box/Option/Insurance.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
21 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box\Option { /** @deprecated */ class Messaging extends \Bpost\BpostApiClient\Bpost\Order\Box\Option\Messaging {} } // src/Bpost/Order/Box/Option/Messaging.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
22 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box\Option { /** @deprecated */ class SaturdayDelivery extends \Bpost\BpostApiClient\Bpost\Order\Box\Option\SaturdayDelivery {} } // src/Bpost/Order/Box/Option/SaturdayDelivery.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
23 
namespace TijsVerkoyen\Bpost\Bpost\Order\Box\Option { /** @deprecated */ class Signature extends \Bpost\BpostApiClient\Bpost\Order\Box\Option\Signature {} } // src/Bpost/Order/Box/Option/Signature.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
24 
namespace TijsVerkoyen\Bpost\Bpost\Order { /** @deprecated */ class Customer extends \Bpost\BpostApiClient\Bpost\Order\Customer {} } // src/Bpost/Order/Customer.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
25 
namespace TijsVerkoyen\Bpost\Bpost\Order { /** @deprecated */ class Line extends \Bpost\BpostApiClient\Bpost\Order\Line {} } // src/Bpost/Order/Line.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
26 
namespace TijsVerkoyen\Bpost\Bpost\Order { /** @deprecated */ class ParcelsDepotAddress extends \Bpost\BpostApiClient\Bpost\Order\ParcelsDepotAddress {} } // src/Bpost/Order/ParcelsDepotAddress.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
27 
namespace TijsVerkoyen\Bpost\Bpost\Order { /** @deprecated */ class PugoAddress extends \Bpost\BpostApiClient\Bpost\Order\PugoAddress {} } // src/Bpost/Order/PugoAddress.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
28 
namespace TijsVerkoyen\Bpost\Bpost\Order { /** @deprecated */ class Receiver extends \Bpost\BpostApiClient\Bpost\Order\Receiver {} } // src/Bpost/Order/Receiver.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
29 
namespace TijsVerkoyen\Bpost\Bpost\Order { /** @deprecated */ class Sender extends \Bpost\BpostApiClient\Bpost\Order\Sender {} } // src/Bpost/Order/Sender.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
30 
namespace TijsVerkoyen\Bpost { /** @deprecated */ class Exception extends \Bpost\BpostApiClient\Exception {} } // src/Exception.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
Deprecated Code introduced by
The class Bpost\BpostApiClient\Exception has been deprecated with message: Use BpostException

This class, trait or interface has been deprecated. The supplier of the file has supplied an explanatory message.

The explanatory message should give you some clue as to whether and when the type will be removed from the class and what other constant to use instead.

Loading history...
31 
namespace TijsVerkoyen\Bpost { /** @deprecated */ class FormHandler extends \Bpost\BpostApiClient\FormHandler {} } // src/FormHandler.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
32 
namespace TijsVerkoyen\Bpost { /** @deprecated */ class Geo6 extends \Bpost\BpostApiClient\Geo6 {} } // src/Geo6.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
33 
namespace TijsVerkoyen\Bpost\Geo6 { /** @deprecated */ class Day extends \Bpost\BpostApiClient\Geo6\Day {} } // src/Geo6/Day.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
34 
namespace TijsVerkoyen\Bpost\Geo6 { /** @deprecated */ class Poi extends \Bpost\BpostApiClient\Geo6\Poi {} } // src/Geo6/Poi.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
35 
namespace TijsVerkoyen\Bpost\Geo6 { /** @deprecated */ class Service extends \Bpost\BpostApiClient\Geo6\Service {} } // src/Geo6/Service.php
0 ignored issues
– show
Coding Style Compatibility introduced by
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...
36