During hand testing this feature the `fiber` option did not generate a full project [^1]. The linting jobs did pass but I think this qualifies as a 'flaky' test to me. Maybe these tests need to also include a build test of the generated project to make sure the application stays functional.
[^1]: the <- got sanitized into <- since the template expects to output html
[^1]: the
<-
got sanitized into<-
since the template expects to output htmlOriginally posted by @MitchellBerend in https://github.com/Melkeydev/go-blueprint/issues/192#issuecomment-1967586592
A build step after generating the project should do the trick, during testing I felt a false sense of security since all the tests passed.