Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.**actually for version 2.x**
Currently we're iterating through every item we get back from an API call and flattening all the nested elements. This adds a lot of code to the views query plugin that is very specific to the method used and requires a bunch of extra iterations.
It **should* be possible to leave the response elements as they are from the API (except perhaps how a single element isn't returned in an array) and give the field handlers enough into to descent into the various attributes as needed.
My initial idea here is to use the 'real field' attribute in the data definition to point at the base of where the data we want lives on an item, and then provide some other meta-data on the handler that describes the rest of the path to the data the handler needs.
Comments
Comment #1
gddHm I will look into the 'real field' property. This was my first serious experience writing Views plugins, so I'm not completely versed in all the options. I fully agree it would be much nicer to do something like this than have to iterate and flatten all the data in advance.
Sorry about the delay, moving overseas is really eating my life these days.
Comment #2
gdd