feat: add Range field to Element parser nodes#1236
Merged
Conversation
a-h
approved these changes
Aug 15, 2025
dgrundel
added a commit
to dgrundel/templ
that referenced
this pull request
Aug 16, 2025
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
2 participants
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.
Hi again, back with another
Rangeaddition. This is the big one, haha.Thank you for the reviews!
Use case notes: As mentioned previously, I'm working on a linting tool for Templ.
Elementseems like the most obvious in terms of being generally useful for such a tool, but I'll also throw out a few things in particular I'm thinking of.<iframe>s. Or, in our case, we plan to have our own custom element replacements for certain tags to ensure compatibility and accessibility for clients and we want to ensure folks can't use the standard elements.altfor<img>andhreffor<a>. (I realize that dynamic attributes can make this challenging/impossible.)<a>inside another<a>) is invalid HTML and can lead to unexpected behavior.