-
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
refresh use setWhere #1224
refresh use setWhere #1224
Conversation
is ☝️ still an issue? (ref) |
Looks like it does not close the popup: ... which is preferable according to the original issue. In the example in the recording (where the feature was removed), however, it would probably be preferable to close it. The preference on what you'd want it to do depends on the specific edits that have happened between the original layer load and the refresh I guess. |
awesome. great job tackling an old chestnut. 🔩
agreed. i wouldn't expect the library to be clever enough to close the popup because the feature was removed upstream. |
I like the way these changes are headed in relying on |
I think I discovered the issue: the
|
@jwasilgeo I think we have discovered a separate issue specifically around editing in esri-leaflet and the If you take the editing out of the picture by using this app to do all editing: |
Thanks for the additional debugging and clear info, @gavinr. I agree with and can verify what you've uncovered. |
refresh use setWhere
refresh use setWhere
trying to address #665, taking advantage of the code in
setWhere()
- there may be a catch here that I'm missing though, would love your input @patrickarlt @jgravoissample.html