Advanced elements should not have the HTML tag voidness checking#381
Merged
hayleigh-dot-dev merged 1 commit intolustre-labs:mainfrom Oct 5, 2025
Merged
Advanced elements should not have the HTML tag voidness checking#381hayleigh-dot-dev merged 1 commit intolustre-labs:mainfrom
hayleigh-dot-dev merged 1 commit intolustre-labs:mainfrom
Conversation
Collaborator
|
Thank you! |
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.
When I render an advanced element with
element.advanced("", "link", [], [contents], False, False), silly as it may seem, it should not be void. It should instead be<link>contents</link>.The checking is maintained for
element.elementandelement.namespaced. The same changes are done for the keyed functions.