Doesn’t it always need to be a method for it to reference the node?
I.e. child() should be node.child(), but foo.baz would not.
> On Aug 7, 2018, at 1:12 AM, Alex Harui <aha...@adobe.com.INVALID> wrote:
>
> Yep, we need more intelligent understanding of when a reference is to the
> node or not.
>
> Debug into EmitterUtils.writeE4xFilterNode and figure out the node pattern
> you need.
>
> -Alex
>
> On 8/6/18, 3:09 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>
> var folderFolders:XMLList =
> assetXML.folder.(child('key').indexOf(folder.key) == 0);
> var folderImages:XMLList =
> assetXML.image.(child('key').indexOf(folder.key) == 0);
>
> Is now compiled as:
>
> var /** @type {XMLList} */ folderFolders =
> this.assetXML.child('folder').filter(function(node){return
> (node.child('key').indexOf(node.folder.key) == 0)});
> var /** @type {XMLList} */ folderImages =
> this.assetXML.child('image').filter(function(node){return
> (node.child('key').indexOf(node.folder.key) == 0)});
>
> “node.folder.key” is not correct. “folder” is a local variable of an un
> related object type.
>
> I assume this broke with the recent XML filter changes.
>
> Harbs
>
