Custom Validation Attributes

[GaProgMan]

Description

Rather than using the if conditions at lines 29 and 49 of the BookController.cs file, implement a set of custom validation attributes.

This work is to be done after #6 (create integration tests)

High-Level Proposed Solution

• Two custom attributes to be created:
  • One which ensures validity fo a provided GUID
  • One which ensures validity of a provided PagedRequest instance

Considerations

• Follow the guidelines at the official documentation for Custom Attributes in ASP .NET Core
• Unit and integration test coverage must not go down by more than 15%

Requirements

• Create a custom attributes for checking whether an input GUID is valid
  • Perhaps called ValidGuidAttribute or similar
  • A valid GUID is:
  • Not empty
  • Not default
  • Is a GUID
• Create another custom attribute for checking whether the PagedRequest instance is valid.
  • Perhaps called ValidPagedRequestAttribute
  • A valid instance of PagedRequest has:
  • A PageNumber value which is greater than 0
  • A PerPage value which is greater than 0
• Both attributes are used, where applicable in the BookContolller class
• Unit and Integration tests are created to ensure that they are both tested and utilised fully