Remove all custom Exception classes, use built-in Exceptions instead. For instance, instead of throwing an Graphp\Graph\Exception\InvalidArgumentException, a method will now throw an InvalidArgumentException. The custom Exception classes did not provide any functionality over the built-in Exception classes and in fact already implemented the built-in ones, so the BC impact should be limited.
The Graphp\Graph\Exception\NegativeCycleException is the only Exception class that used to provide any functionality. However, this is better off in the graphp/algorithms package instead as per #119.
Remove all custom Exception classes, use built-in Exceptions instead. For instance, instead of throwing an
Graphp\Graph\Exception\InvalidArgumentException, a method will now throw anInvalidArgumentException. The custom Exception classes did not provide any functionality over the built-in Exception classes and in fact already implemented the built-in ones, so the BC impact should be limited.The
Graphp\Graph\Exception\NegativeCycleExceptionis the only Exception class that used to provide any functionality. However, this is better off in the graphp/algorithms package instead as per #119.