-
Notifications
You must be signed in to change notification settings - Fork 799
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
L.esri.FeatureLayer addfeature and removefeature events not fired at all #788
Comments
currently, 'add' and 'remove' events are only fired when individual features are appended or dropped from the current collection of a a proposed fix can be found in #790. once its merged, it will appear in our next tagged release (2.0.1) afterward, i should be able to find some time to backport and create a |
Hi, @jgravois! That's awesome! Thank you for having the time to look into it! It would be great to count on a Thank you very much for your reply and work. Say 'hi' for all the good fellow from Esri on my behalf. |
the fix has been merged into |
That's beautiful, @jgravois! Thank you very much for your quick action and backporting. |
L.version
): 0.7.7L.esri.VERSION
): 1.0.3Steps to reproduce the error:
What happens is that labels are kept on map even after the parent layer was disabled.
I was expecting that
addfeature
andremovefeature
could work to add and remove labels when enabling/disabling the parent layer. These events are never fired tough, as even theconsole.log
messages aren't throw. Is there a bug with these events?The text was updated successfully, but these errors were encountered: