I appreciate the feedback.
That is a good use of filters. I think I’ll take your approach.
Worth noting, if I apply your example to my use case, I end up with:
With our API, I enforce the standard that the key needs to be one that is present on the resource attributes. The only issue one could raise with you approach is that the assumption becomes the resource attribute precedes the underscore
Basically, the following is the equivalent to an opening range.
Overall, I like it.