Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't pre-resolve and index complex locationSets into GeoJSON #9347

Merged
merged 1 commit into from
Oct 28, 2022
Merged

Don't pre-resolve and index complex locationSets into GeoJSON #9347

merged 1 commit into from
Oct 28, 2022

Commits on Oct 28, 2022

  1. Don't pre-resolve and index complex locationSets into GeoJSON. 

    This was taking a lot of time at app startup.

Instad now we resolve and index only the include and exclude parts.
We can still determine the valid locationSets at runtime in `locationSetsAt()`
by checking the `_locationIncludedIn` and `_locationExcludedIn` caches.

This also upgrades the locationManger to an ES6 class.

This also includes some hacky code in nsi.js so that the NSI will continue to work.
The NSI matcher can build its own location index, but it doesn't need to do this.
We monkeypatch a few of the matcher collections to work with the new LocationManager.
    @bhousel
    bhousel committed Oct 28, 2022
    Configuration menu
    Copy the full SHA
    2b2a71f View commit details
    Browse the repository at this point in the history