Skip to content

Print invalid generated code during panic#446

Merged
GuillaumeGomez merged 1 commit intoaskama-rs:masterfrom
Kijewski:pr-parse-source-crash
May 19, 2025
Merged

Print invalid generated code during panic#446
GuillaumeGomez merged 1 commit intoaskama-rs:masterfrom
Kijewski:pr-parse-source-crash

Conversation

@Kijewski
Copy link
Copy Markdown
Member

No description provided.

@Kijewski Kijewski force-pushed the pr-parse-source-crash branch from f9f86b6 to f4aa0ce Compare May 19, 2025 06:18
@Kijewski Kijewski changed the title Print invalid generate code during panic Print invalid generated code during panic May 19, 2025
@GuillaumeGomez
Copy link
Copy Markdown
Collaborator

Please add a UI test. :)

@GuillaumeGomez
Copy link
Copy Markdown
Collaborator

Oh wait, might be tricky to do that. Hum... Is there a way to add such a test?

@Kijewski
Copy link
Copy Markdown
Member Author

I don't think so. Any input that would cause the panic, so it can be caught in a UI test, would be a bug that needs to be fixed.

@GuillaumeGomez
Copy link
Copy Markdown
Collaborator

Yeah that's what I figured out. Unless we voluntarily add a failing case in our code generator, not possible. Don't think it's worth it so nothing more we can do here. Very good idea, thanks!

@GuillaumeGomez GuillaumeGomez merged commit 6ac39d2 into askama-rs:master May 19, 2025
38 checks passed
@Kijewski Kijewski deleted the pr-parse-source-crash branch May 19, 2025 14:49
@Kijewski Kijewski mentioned this pull request Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants