forged-collections/exceptions

Exception interfaces and classes common to ForgedCollections.

Maintainers

Details

gitlab.com/forged-collections/components/Exceptions

Source

Issues

Installs: 3

Dependents: 0

Suggesters: 0

Security: 0

Stars: 0

Forks: 0

dev-master / 0.1.x-dev 2024-12-13 19:15 UTC

Requires

  • php: ^8.2

Requires (Dev)

MIT 332f5d9dc747f3b04aab78c76248082a5473ada9

exceptions

This package is auto-updated.

Last update: 2025-04-13 19:58:19 UTC

README

Exception philosophy (or is it methodology?)

TODO: explain my philosophy and principals for Exceptions implementation and handling.

Dependencies

None.

Installation

composer require forged-collections/exceptions09

Usage

TODO

Testing

Testing is performed by PhpUnit and run in Docker containers, one for each supported version of PHP.

To run all tests for all PHP versions:

docker compose --profile=phpunit up

That command tests all PHP version in parallel, which can make understanding the rest output difficult. To work around this either run them individually (or see Test Reports):

# Run PHP 8.3 test only
docker compose --profile=phpunit up phpunit83

Test reports

Multiple reports are written for each PHP version.

  • /build/<php-version>/testdox.txt : Human friendly plaintext report of passed/failing tests.
  • ./build/<php-version>/testdox.html : As above, but formatted with HTML.
  • ./build/<php-version>/coverage : Project's test coverage report in HTML
  • ./build/<php-version>/compose.lock : Copy of composer's lock file for local replication and debugging.

You can also see the test runners actual output with the command:

docker compose --profile=phpunit logs <container>

For example to see the output from PHP 8.3

docker compose --profile=phpunit logs phpunit83

Debugging tests

TODO