I'm thinking it might be better off splitting it into two different features.
1. Creating a stream of resources from a given resource
2. Language which will creates a Predicate which could apply to any
given Stream regardless of the source of the stream
But yeah, for the second which I see as
Hi Jason,
On Thu, 2018-01-25 at 12:35 -0500, Jason E Bailey wrote:
> Another one of my side projects
>
> https://github.com/JEBailey/sling-resourcelocator
>
> I think there's enough difference between other ways of finding
> resources that there's value to bringing it in. But I like
> feedback
efan
>
> [1] https://sling.apache.org/documentation/bundles/sling-query.html
>
>
> >-Original Message-
> >From: Jason E Bailey [mailto:j...@apache.org]
> >Sent: Thursday, January 25, 2018 6:35 PM
> >To: dev@sling.apache.org
> >Subject: Gauging inte
> >Sent: Thursday, January 25, 2018 6:35 PM
> >To: dev@sling.apache.org
> >Subject: Gauging interest on Yet Another Way to Find Resources
> >
> >Another one of my side projects
> >
> >https://github.com/JEBailey/sling-resourcelocator
> >
> >
>Sent: Thursday, January 25, 2018 6:35 PM
>To: dev@sling.apache.org
>Subject: Gauging interest on Yet Another Way to Find Resources
>
>Another one of my side projects
>
>https://github.com/JEBailey/sling-resourcelocator
>
>I think there's enough difference between other w
Another one of my side projects
https://github.com/JEBailey/sling-resourcelocator
I think there's enough difference between other ways of finding
resources that there's value to bringing it in. But I like feedback,
since I'm a bit prejudiced.
It works by creating a Java8 Stream of resource obje
