Filter parameters

[MGatner]

Filters can take parameters?? Anywhere this is documented? I dug through the CI4 Router code but there’s a lot of different pieces there...

[lonnieezell]

Yeah, the Router has gotten a bit complex :)

I actually built the feature for it to support parameters based on me making this auth-lib. One of the benefits of developing the core at the same time. It doesn't look like that got in the docs, though. The ability to use filters in route groups made it in, but not the ability to have parameters in the docs.

Thanks for pointing that out. Will have to remedy that!

[MGatner]

That’s great! Definitely a needed feature. It looks like it is basically filterName:parameter - I do see that it can receive multiple parameters so is that a CSV? Also, any chance it can take dynamic parameters? E.g. a segment of the route (if you wanted a filter to respond differently based on the target content)

[lonnieezell]

That is the correct format, and yes it supports CSV. Dynamic values is not currently supported, and I didn't have any plans to, either, but I wouldn't turn away a well thought-out PR for that :) Though that could start getting pretty complex considering the location in the flow that routing occupies....

[MGatner]

Great - I’ll work up a PR for the user docs and give some thought to dynamic parameter values. Thanks for the feedback.

[MGatner]

After poking at this for a while, I kept coming back to the same conclusion: Dynamic filter parameters is replicating controller functionality which should probably stay with the controller. Parameters (generally) are awesome because they save a lot of potential duplicate code across controllers and controller methods, so I will still send over a PR for the user docs on that.

[MGatner]

Parameters don't seem to be supported by app/Config/Filters.php - does that seem correct?