I know this is a very old support request, but I ran across this today and thought I'd drop a link here to the solution in case someone else is trying to figure out how to do this:
https://drupal.stackexchange.com/questions/232156/how-to-add-filters-to-...
Basically, you'll want to add a form to your $build array inside your render() method (of your class that extends the EntityListBuilder class) with formBuilder()->getForm().
Make your form add some filters via query parameters and then a getEntityListQuery() method that will construct a query to apply to the list.
I agree that this can probably be handled better, but until a better solution is provided, I went ahead and rebased the temp fix on to the Drupal 10.3.x branch for those that need a compatible patch.
Thank for the speedy response! It turns out that when using this module alone, UserAuth->authenticate() does not seem to get called. So, there is no error.
I ran across this when doing testing with the simple_oauth module. This does get called via simple_oauth. So, I guess this is a nothing-burger and the overridden UserAuth->authenticate() that is in this branch should maybe be removed; but that is for another issue.
provided a link to MR 41
This patch fixed this issue for me. LGTM!
...we will be discontinuing one of the modules.
Has it been decided on which module will be discontinued?
Looks like the parent issue for this has been resolved. Has there been any work done on this issue? I'll be building the feature for a site but wanted to check in to see if anyone has worked on this at all. I'll do my best to make it non-site specific and most likely as its own module rather than patching commerce_shipping module directly. Thoughts?
While the MR/patch, and the improvement suggested above, does make the warnings go away—it does not get to the root of the issue.
The question, for me, is what does `draggableviews_structure_parent` represent and when/where is it ever set to a value? `$row` in this context is of type `\Drupal\views\ResultRow` which does not have the `draggableviews_structure_parent` property. Most other usages of this property also have protections around it. Do we need the `draggableviews_structure_parent` property at all? What use/test case am I missing here?
Thanks!
Oops, that last file had some email info in it: here's the plain diff.
And here's the updated patch for those that use patch based workflows until this gets merged.
Patch from #9 works like a charm. Thanks for the patch!
Is there any headless Drupal project, that is not using "JSON:API Extras"?
@mogio_hh it seems that Druxt does not use JSON:API Extras, FWIW. Personally, I've gone away from JSON:API Extras as well because I don't really like modules that just make a bunch or random tweaks. Yes, they are convenient, but don't add much value beyond that, IMO.