Storing dict keys during traversal about glom HOT 3 CLOSED

Ah, the grandparent key, sure! This isn't as pretty as I would like, but here's the working spec:

(
        T.items(), 
        Iter(
          (A.globals.gp_item, T[1].values(), 
           Iter({'val': 'c', 
                 'path': S.globals.gp_item[0]}))
        ).flatten().all()
)

And I get:

[
    {
        "val": 1,
        "path": "a"
    }
]

Here's a link to a glompad where you can fool around with it in your browser.

Two key things to note:

• I'm using the globals member of the scope (and the A assignment shortcut) to save the grandparent item before we descend. Probably when you used S the value was being lost because the scope was local.
  • If this is part of a much larger spec, you can create your own non-local, non-global scope with Vars documented in the link above.
  • I found it simpler to save the grandparent item (key and value), instead of just the value, and then only emit the key (gp_item[0]).
• Notice I'm using two Iter specs. glom doesn't yet have full tree traversal, so the nesting of the spec is going to roughly match the nesting of your data. If you need this to work in an arbitrary nested structure, I recommend remap, the recursive map function, part of boltons.iterutils.

Hope this helps!

from glom.

Thanks a lot, I almost reached that one myself! For some reason I was focused on trying to save just the key T[0] instead of the whole items structure, this works.

And a related thank you for that great library.

from glom.

Yeah, I know what you mean re: keys vs items. I might add this example to the docs, in case it's instructive for others too :)

from glom.