fix: Correctly parse nested attribute and tag sources. #293
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.
What
This PR fixes an issue with nested attributes (such as those used by CoreTable) not being resolved correctly.
More specifically, it:
::parse_attribute()
is called correctly regardless of if there is aselector
present.tag
sourcesAdditionally, tests have been backfilled specific CoreTable attributes.
Why
Fixes #282
Test Coverage
Important
This PR is based on #284 which should be merged first.
Relevant diff 1192a61
Covered
CoreTableAttributes
Not covered
CoreTableAttributes.metadata
Additional notes:
The new
DOMHelpers::get_first_node_tag_name()
is marked as internal, because the entire class needs to be reworked (and ideally replaced with WordPress's HTML parsing api ).