In its current instance, the render_patterns command stops execution as soon as a template fails to render.
Describe the solution you'd like
While this might be suitable as a basic check, it would be better for it to keep processing other patterns, displaying errors along the way, and then returning with an error status code.
At the same time it would be nice to consider whether:
The current "fail fast" behavior should be kept under a flag or not (it’s a common feature of test runners, but I’m unsure of its usefulness here)
Whether there should be a way to ignore failures in specific patterns, or provide input to the command so only specific patterns are processed (allowlist/blocklist or similar). While at first I didn’t think this would be useful, it would probably help adopting the command.
Describe alternatives you've considered
Fix all patterns 😬
Additional context
This would also be a good occasion to review the output of the command to check whether it’s suitable or not.
Is your proposal related to a problem?
In its current instance, the
render_patternscommand stops execution as soon as a template fails to render.Describe the solution you'd like
While this might be suitable as a basic check, it would be better for it to keep processing other patterns, displaying errors along the way, and then returning with an error status code.
At the same time it would be nice to consider whether:
Describe alternatives you've considered
Fix all patterns 😬
Additional context
This would also be a good occasion to review the output of the command to check whether it’s suitable or not.