hallo jason. this looks a bit like sling-query [1], although the syntax is a bit different. how do you compare those two approaches?
stefan [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 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 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 > >And because it uses resources it's resource provider agnostic. > >- Jason >
