Fix. Account for the "data_array" property of the "values" attribute of the "dimensions" attribute. Closes #2385 #2387
+75
−3
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 PR proposes a fix to account for the "data_array" property of the "values" attribute of the "dimensions" attribute used in special traces like "parcoords", "parcats" and "splom" traces thereby closing #2385.
Currently, when an attribute has the "data_array" attribute it gets wrapped in
AsIs
insideverify_attr
. However, this check gets skipped for thedimensions
attribute as it is an unnamed list. Additionally, the schema specs for thevalues
attribute are somewhat nested.To account for that the PR adds some special treatment for
dimensions
attribute toverify_attr
which useslapply
to loop over the items of thedimensions
list.With the proposed fix the examples documented in #2385 work fine, e.g. for
"parcats"
:Created on 2024-08-31 with reprex v2.1.1