Open Denperidge opened 1 year ago
We should definitely handle this better.
I think the cause is that we're importing service code here, but failure to import (as you say because of a missing requirement but also because of syntax errors for example) doesn't cause the service to fail, Flask still sets up the app, just without any routes (that's why everything ends up returning a 404).
Would it be better to have the service not boot up at all if there's an error importing the service code? I'm not sure how such errors are handled in other templates.
Steps to recreate:
Output:
If possible, a clearer error as to where the lack of functional routes comes from would be optimal