-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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.
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
eliminate need for "interactive" property on layers #1479
Comments
I did some profiling and memory usage is fine when we remove The main task updating the style spec: mapbox/mapbox-gl-style-spec#418 Should we wait until the spec is changed and released or can we start ignoring it immediately? |
I don't think we need to wait until the spec is changed. That said, we do need to think carefully about this because it is a breaking change. Users who do not pass a |
🎉 🎉 🎉 this is excellent news thx @ansis |
All layers should support
featuresAt
automatically. Behind the scenes the necessary datastructures should be built lazily, or however makes sense for performance.Having a user-visible
interactive
layer property leaks implementation details to the API, is a big trap for users, and leads to convoluted examples like this.The text was updated successfully, but these errors were encountered: