joebengalen/payload

Domain payload library

Payload

, _(*1)

Payload is a data transfer object between the domain layer and the application layer. The idea is that for every method you call on the domain service/access layer (domain API), you will receive a Payload instance as answer., _(*2)

Installation

Via Composer, _(*3)

bash $ composer require joebengalen/payload, _(*4)

Usage

Fetch vs Command methods

There are two types of methods in a domain access layer: First you have fetch methods, which asks for data. Second you have command methods, which tell the domain to perform a certain action. The Payload status will tell you if the method was successful or not. Apart from the status the Payload may contain additional information, such as the requested data or an exception if something went wrong., _(*5)

Payload status

The Payload status can be set and read with the following methods:, _(*6)

• setStatus($status)
• getStatus()

The following Payload statuses are available., _(*7)

• PayloadStatus::FOUND Requested data found
• PayloadStatus::NOT_FOUND Requested data not found
• PayloadStatus::SUCCESS Action succeeded
• PayloadStatus::INVALID Invalid input
• PayloadStatus::ERROR Error during execution

WARNING: Do not rely on the constant values as they may change over time! Always use the constants by their name., _(*8)

PayloadFactory

To make the creation of the Payload objects easier there is a PayloadFactory available. This factory contains methods to create payload objects with every available status or one without a status., _(*9)

• createPayload() Create a new Payload object
• createSuccessPayload() Create a new Payload object with status success
• createFoundPayload() Create a new Payload object with status found
• createNotFoundPayload() Create a new Payload object with status not found
• createInvalidPayload() Create a new Payload object with status invalid
• createErrorPayload() Create a new Payload object with status error

Payload data

Apart from the status the Payload can contain a message, the input and the output of the domain method. To manage that data the following methods are available in the Payload class., _(*10)

• setMessage(string $message)
• getMessage()
• setInput(mixed $input)
• getInput()
• setOutput(mixed $input)
• getOutput()

PayloadInterface

Payload objects should only be created and modified within the domain. If the domain method has PayloadInterface as return type, only the getter methods will be visible/available to the application., _(*11)

Of course you could still modify the payload by methods outside of the interface, but it will at least show you should not use the setter methods., _(*12)

Best practice

Explanation of how I intended the Payload objects to be used. You can make up your own set of rules, but it is recommended to use the same rules throughout the whole domain., _(*13)

Payload status

Fetch methods can return the following payload statuses - PayloadStatus::FOUND - PayloadStatus::NOT_FOUND - PayloadStatus::INVALID - PayloadStatus::ERROR, _(*14)

Command methods can return the following payload statuses - PayloadStatus::SUCCESS - PayloadStatus::INVALID - PayloadStatus::ERROR, _(*15)

Payload input/output

For each payload status the following input/output data should be provided, _(*16)

• PayloadStatus::FOUND, _(*17)

  • input: null or named array of fetch parameters (if any)
  • output: found entity or collection

• PayloadStatus::NOT_FOUND, _(*18)

  • input: named array of fetch parameters (if any)
  • output: null

• PayloadStatus::SUCCESS, _(*19)

  • input: null
  • output: created/updated/deleted entity or other relevant data if available

• PayloadStatus::INVALID, _(*20)

  • input: named array of the parameters
  • output: list of error messages

• PayloadStatus::ERROR, _(*21)

  • input: named array of the parameters
  • output: thrown exception

This way you will always have the information you may need. If anything goes wrong (not found, invalid or error status) you will have the input parameter to see why. Optionally you may choose to always include the input argument in the payload., _(*22)

Payload message

Payload messages are optional. They may contain a general message about the status. Such a message could be handy to provide the user with a friendly message in the application. I would recommend to at least be consistent throughout the whole domain whether you return a message or not., _(*23)

Examples: - Could not find user - User was successfully updated - Message successfully marked as read - Invalid comment data provided - Could not add project, _(*24)

Change log

Please see the CHANGELOG for more information what has changed recently., _(*25)

Testing

This project uses PHPSpec for testing., _(*26)