Skip to content

piperename with numeric indexes are order dependent #22

Description

@thwarted

pipe 11278a7cb21e7964282dfe9a46f38837

I have a rename yahoo pipes module that looks like:

item.p.span.0 Rename title
item.p.span.1 Rename description

p.span has two children. These are evaluated in this order, and because this is a rename, p.span.0 gets deleted after being assigned to title. As this is a list, the list length decreases by one, causing the rename of p.span.1 to fail because there isn't a p.span.1 after the deletion, there's only p.span.0.

yahoo's rename module seems to handle this. I guess a work around is to reorder the renames so that the highest numbered one in each group is done first, so only the last item in the list is deleted, keeping the later indexing consistent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions