Array modifier order matters, but shouldn't

[curtisblackwell]

Expected behaviour

I should be able to place my modifiers in any order and get the same results.

Actual behaviour

Placing offset after limit returns unexpected results.

Steps to reproduce

1. Have an array.
2. Iterate over that array with a set limit and offset (with limit first).

[jackmcdade]

Nope, Modifiers are 100% order dependent by design.

[curtisblackwell]

😢 :trombone:

[jackmcdade]

Think about it. Each modifier modifies the data and then sends it back. If you offset and then limit, or limit and then offset, you're going to have two totally different results.

[jasonvarga]

{{ string | backspace:2 | reverse }}

Without order, what would you expect to happen here?

[curtisblackwell]

I guess I just don't see why the order should matter for limit and offset. When would you ever want to limit then offset? Though it's definitely not worth breaking the mold over.

[jackmcdade]

Those would be maybe the only two you'd want to work that way. And then we'd need to find a way to make them bypass the normal Modifier logic, and then document that those two are special... best to just order them as you will, and move on.

[curtisblackwell]

Right, I agree. Just didn't think of them as modifiers since I wrote them like parameters.