- Issue created by @droath
- Merge request !11Fix issue to allow entity extra field view arguments to support multiple optional arguments. → (Open) created by droath
- Status changed to Needs review
7 months ago 4:10am 12 December 2023
When passing View arguments using token values, it could be a single value or multiple values. For example, if you have multiple taxonomy term IDs like NULL/NULL/7876, you will need to pad the empty values with null if they are optional. This will still allow the view to respect the only filter. But if you had NULL/NULL/NULL, then no results will be shown from the view. I was able to solve this issue by setting empty values as 'NULL' and then checking to see if only those values, if only NULL values were defined, then I would just pass along an empty array which allows the view to render content without any contextual filters applied.
Needs review
2.0
Code