Skip to content

Technical debt/future considerations #90

@ollieread

Description

@ollieread

This is all the “technical debt” or future considerations off the back of the initial work.

  • The unit tests can be refactored to use mocks and fakes over models and actual database entries.
  • The ServiceOverrideManager will need a dedicated unit test
  • I don't like the current documentation, as it reads more like a technical breakdown than a walkthrough like Laravel

Metadata

Metadata

Assignees

Labels

status: planningThe issue is being planned for the futuretype: fixFix for a bug or other issuetype: refactorRefactoring of code

Type

No type

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions