Agreed, the way this is returned makes it very difficult to map to a headless frontend.
{
"#states": {
"visible": {
".webform-submission-newsletter-add-form :input[name=\"country\"]": {
"value": "AU"
}
}
}
}
Theoretically you could parse .webform-submission-newsletter-add-form :input[name=\"country\"] but it's unfortunate that this is a CSS targeting rule instead of a more appropriate JSON structure nested under the field name.
Hey just chiming in to say this is definitely happening, and the solution of adding an extra sort on a unique field does indeed seem to resolve the issue. Thanks!
Glad to see others talking about - our use case would be to know what exposed filters exist on the view and what vocabularies they reference in order to programmatically build those exposed filters on the front end, rather than hardcoding.
I can get this information from the `view--view` like you say, but it would be pretty slick the metadata of the view was available alongside the data.