Dev Tools: Show warnings for Compile-Time Optimization Mismatches#1660
Merged
Conversation
🌿 Interactive Playground and Documentation PreviewA preview deployment has been built for this pull request. Try out the changes live in the interactive playground: 🌱 Grown from commit ✅ Preview deployment has been cleaned up. |
commit: |
This was referenced Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request adds compile-time optimization mismatch detection and reporting to the Herb dev tools.
When
verify_optimizationsis enabled in ReActionView, the template handler compiles each template twice on first render, once with optimizations and once without, and compares the output. If the results differ, a<template data-herb-optimization-mismatch>marker is injected into the page.The dev tools detect these markers and display a warning badge (⚠️ ) next to the Herb floating menu. Clicking the badge shows a panel listing the affected templates by relative path. Full diff details are logged to the Rails server log.