web: make applyAttrs
in the second overloaded TagElement
nullable to be consistent with the first one
#1814
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.
From what I understand, for non-inline functions passing
null
is a bit more efficient than passing an empty lambda, and that's why most functions in this library have the signatureattrs: AttrBuilderContext<HTMLElement>? = null
. Then there is no reason the second overloadedTagElement
function shouldn't be like that, so I guess this is a small mistake that should be fixed.