sprout
sprout copied to clipboard
Technical debt/future considerations
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
ServiceOverrideManagerwill 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
Address test coverage mentioned here: https://github.com/sprout-laravel/sprout/pull/112/#issuecomment-2686325730