When you have templates included in templates, the errors become quite difficult to understand as we don't know which file is triggering it. With this change, it adds the path of the file where the error is located:
error: problems parsing template source in `templates/core/about/builds.html` at row 34, column 32 near:
"=\"rust\") %}{% filter dedent(levels=3) -%"...
--> src/web/sitemap.rs:109:10
|
109 | #[derive(Template)]
| ^^^^^^^^
|
= note: this error originates in the derive macro `Template` (in Nightly builds, run with -Z macro-backtrace for more info)
Making my life and very likely everyone else's better. :)
Sadly, I can't enforce it with trybuild as it only allows to have inline tests (because the folder where the ui tests are run is different and I couldn't find a way to do it...).
When you have templates included in templates, the errors become quite difficult to understand as we don't know which file is triggering it. With this change, it adds the path of the file where the error is located:
Making my life and very likely everyone else's better. :)
Sadly, I can't enforce it with
trybuild
as it only allows to have inline tests (because the folder where the ui tests are run is different and I couldn't find a way to do it...).