Seperate JSON schema from business logic

[ashley-evans]

Valued Added

Improved readability and maintainability of the code base. Improved separation of business logic and input validation.

Description

Currently each of the lambda functions have schema validation that takes place on the input to the lambda function. The schema is often complex and takes up a large amount of the file size.

Therefore, the readability of the solution could be improved by separating the schema validation and business logic into their own files.

Acceptance Criteria

AC01

• Each of the lambda functions which have an input schema are updated to separate the schema and business logic into different files

AC02

• The functionality of the solution should be unaffected. i.e. the automated tests all still pass