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<Resource> which could apply to any given Stream<Resource> regardless of the source of the stream But yeah, for the second which I see as a package, I'll get into the whiteboard. The first one, I'm thinking of a story and a pull request against ResourceUtil. - Jason On Tue, Jan 30, 2018, at 5:19 AM, Robert Munteanu wrote: > 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, > > since I'm a bit prejudiced. > > It works by creating a Java8 Stream of resource objects starting from > > a > > resource that you provide and iterating through descendants based on > > provided criteria. > > 1. Handles limits, ranges, and depth > > 2. Control traversal path by setting conditions on which child > > resource > > can be included3. Can define complex acceptance criteria for > > resources based on > > properties4. Definable via fluid api or a filtering language > > 5. filtering language is extensible using custom functions > > IMO you can add it to the whiteboard, and we can further discuss its > evolution once you think it's ready for a first release. > > Thanks, > > Robert
