Set Filter method for GeoJSON Source

[Ruschio]

Adding setFilter method for GeoJSON source, to allow filtering data without passing new ones with setData function

Launch Checklist

• Make sure the PR title is descriptive and preferably reflects the change from the user's perspective.
• Manually test the debug page.

[CLAassistant]

All committers have signed the CLA.

[stepankuzmin]

Hi @Ruschio,

Thanks for the contribution, looks good to me 👍
Could you please rebase your changes on top of the latest main branch so we ensure all the tests are passing? Thanks!

[5andr0]

This needs a bump! Would be nice if this gets implemented soon

[Ruschio]

Hi @Ruschio,

Thanks for the contribution, looks good to me 👍 Could you please rebase your changes on top of the latest main branch so we ensure all the tests are passing? Thanks!

@stepankuzmin I rebase this pull request to the actual main branch, so that it can be included after tests.
However, I noticed that performing multiple setFilter() operations causes some problems in data display. More in detail, seems that data (such as points or icons) remain stucked for certain zoom levels, and for others filter is correctly applied.

[5andr0]

@stepankuzmin I rebase this pull request to the actual main branch, so that it can be included after tests. However, I noticed that performing multiple setFilter() operations causes some problems in data display. More in detail, seems that data (such as points or icons) remain stucked for certain zoom levels, and for others filter is correctly applied.

I can confirm, that when I manualy set the source.workerOptions.filter and call source._updateWorkerData() in the next map.on('render' event the first call to map.querySourceFeatures returns an array including invalid clusters of which features have been deleted and a consecutive call to source.getClusterLeaves throws an invalid cluster id error.

I just catch and ignore that error and wait for the next render, where the source features clusters are updated