I apologize for not being able to get back to this until now. None of the suggested solutions worked for me, but I did end up finding one that worked. Instead of setting orderby.sort to desc as I had, turns out since I set the predicate type to orderby in its constructor, to set the sort order I jus...

I've already checked, it is "desc" just as expected. I've also tried "dec" and "DESC" just to see, but neither have worked. The full creation of the search is: SimpleSearch search = request.getResource().adaptTo( SimpleSearch.class ); if ( search != null ) { String query = this.queryParams.get( "...

I've not hardcoded it in the code itself, but I have tried that while debugging and manually setting values while the code is halted. I've also tried "dec", which I saw either here or StackOverflow and wasn't sure if it was a typo or not, and "DESC" in case case mattered, but neither solved the issu...

I'm having differing results when running a query via the query builder and via a component building the same query, mainly on the order of the results. Setting orderby.sort = desc in the query builder gives me exactly as I would expect, in this case ordering results by publication date starting wit...

I originally had this as a reply to that thread but decided to pull it out into a new one. lukasz-m caught my actual issue with using getPath() rather than getName().

That was exactly it, and looking at previous code that was working I see now that getName() was used, not getPath() like I was using, thank you. And as far as the name generation, I'm using hashes of the paths to salt the node names so there's very little chance of collision, but I'll be sure to che...

I'm attempting to pull a property out of an existing node and use it to create a new titlecore node just before the source node and I'm having an issue with moving the newly-created nodes around within a container, it's throwing an IllegalArgumentException saying that the srcChildRelPath has an inva...

I'm too used to writing JS, I forget this is interpreted differently. That did the trick, thanks!

I'm extending the list core component and implementing pagination and filtering via the JS Use API, but I'm having an issue passing values to the JS. The HTL I have: <sly data-sly-use.list="...TextList"></sly> <sly data-sly-use.pagination="${ 'text-list.js' @ listID = list.id, val = 'red' }"></sly> ...

Why not? That seems like such a fundamental functionality for a list component to have. I'd argue that it's more important than displaying the description.