Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Technical debt/future considerations #90

Open
ollieread opened this issue Jan 25, 2025 · 0 comments
Open

Technical debt/future considerations #90

ollieread opened this issue Jan 25, 2025 · 0 comments
Assignees
@ollieread
Labels
status: planning The issue is being planned for the future type: fix Fix for a bug or other issue type: refactor Refactoring of code

Comments

@ollieread
Copy link
Member

ollieread commented Jan 25, 2025 •
edited
Loading

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
@ollieread ollieread added status: planning The issue is being planned for the future type: fix Fix for a bug or other issue type: refactor Refactoring of code labels Jan 25, 2025
@ollieread ollieread self-assigned this Jan 25, 2025
@ollieread ollieread moved this to Backlog in Sprout Development Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ollieread ollieread

Labels
status: planning The issue is being planned for the future type: fix Fix for a bug or other issue type: refactor Refactoring of code
Projects
Sprout Development
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ollieread