• Build a simple Slimv4 API with one Endpoint
• Endpoint throws multiple Exceptions
• Integrate Bag to handle those for a json:api compliant response

Remove the Slim dependency and replace it with a more independent solution.

Handling a Single Exception is already implemented. Now we also need to be able to handle multiple exceptions:

• Middleware gets an empty bag in the Binding
• Bag will be instantiated once (Singleton in Container)
• Bag will be filled in Handler
• Two ways:
  • try-catch for a Bag-Exception, for errors where one simply does not want to continue
  • Validation if bag has been filled when request is done for multiple possible exceptions during runtime

Remove the JsonApiBody, if it is not necessary anymore.

Relates to Issue #28

Was done with Issue #35.

To be able to implement the Middleware we need a set of test cases:

Cases for "normal" exceptions:

• handle an Exception without a set error code and message
• handle an Exception that defines a not supported HTTP status code
• handle an Exception that defines a correct error code and message

Cases for json:api specific exceptions (JsonApiExceptionInterface):

• handle a json:api Exception with status & title
• handle a json:api Exception with status, code & title
• handle a json:api Exception with status, code, title & detail
• handle a json:api Exception with status, code, title, detail & source
• handle a json:api Exception with status, code, title, detail, source & meta
• handle a json:api Exception with status, code, title, detail, source, meta & ID

Missing:

• Test cases for bag/list exceptions

Define how a bag interface should look like.

What methods do we need?

• push
• add
• remove (any need for this)
• …

• Add an example to showcase the usage of the middleware
• Add the example to the existing examples folder inside the project

Build a simple Laravel API with one Endpoint
Endpoint throws multiple Exceptions
Integrate Bag to handle those for a json:api compliant response

• Source is an array
• Only uses keys "parameter" and "pointer"

Define and implement a generic factory for an json error object.

• https://jsonapi.org/format/#error-objects
• https://jsonapi.org/examples/#error-objects

• Add helper to simplify string comparison
• Replace method "assertJsonStringEqualsJsonFile" with new helper

• Detail is a String
• Can be empty (Default Empty String)

Only setting a flag, which is false per default, the flag will be set via binding
Later on we can think about, using an array instead, with which it can be defined what should be set for e.g. Production

Debug-Flag false: Only Status, Code, Title
Debug-Flag true: Additionally Detail, Meta, Links

• Rename ExceptionBagInterface to ThrowablesBagInterface
• Rename class ExcetionBag to ThrowablesBag

• Add an example to showcase the usage of the middleware
• Add the example in an example folder inside the project

Do the setup for GitHub actions to

• lint the src folder
• test the source code by executing the PHPUnit tests
• prevent force push to master
• prevent merge before all reviews approved

Please make sure to add the status badges for the two actions to the readme.

Create the repository with

• .editorconfig
• composer.json
• .gitignore
• src
• tests

Add an additional PSR-7 middleware for Lumen/Laravel

• Cleanup and rename json files
• Simplify setting up tests with debug flag

Waits for Issue #28

• Move the Stacktrace info of an Exception to the meta-part
• Only if debug-flag is set to true

tbd

Building a simple PSR-15 Middleware:

• where you only have the Request and Handler (https://www.php-fig.org/psr/psr-15/#22-psrhttpservermiddlewareinterface)
• handles a single exception thrown in the Handler