Sorry, I just saw your issue.
Filtering is not something which I intended with this module. I currently don't see how I should fit this into this module, especially as you would need some kind of user interface.
You should clone the module and add filtering to the JavaScript code, it should be easy to implement (the hard bits are user interface, how to update the filtered data when the filter values change, ...).
If you come with a general solution, I might consider it integrating this into this module. So please come back to report on progress.
Sorry, I just noticed your issue. As Leaflet Layers GeoJSON does not use Views, you are wrong here. The Leaflet Views integration which you are using is part of the Leaflet → module.
Thanks for notifying, sorry I didn't see your issue before.
Not sure how that happened in the first place, as the new version was already available at the time when I created the module. Maybe copy&paste from the README.
Anyway, I just fixed the dependency.
I extended the module by twig templates. There's a switch in the configuration, where you can select between tokens or twig templates. I haven't created a patch (yet), for now it is available on Github.
Examples, how you can use it:
{{ entity.field_name[0].value }}{% for v in entity.field_name %}{{ v.value|upper }} {% endfor %}
How shall we proceed? Shall this modification be merged into the module? Shall I create a separate issue with the merge request?
I extended the module by twig templates. There's a switch in the configuration, where you can select between tokens or twig templates. I haven't created a patch (yet), for now it is available on Github.
Examples, how you can use it:
{{ entity.field_name[0].value }}{% for v in entity.field_name %}{{ v.value|upper }} {% endfor %}
Btw, I think I didn't merge the patch as expected. I'm still figuring out how to use this platform. Sorry!
Thanks for contributing your patch! I just merged it :-)