Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
GeocoderService incompatibility between when.js Promise and browser native Promise
See original GitHub issueI have made two examples in Sandcastle, one with browser-native Promise and one with when.js calls. Please load each example, search for anything, then hit Enter. In the browser-native Promise example, the bar continues to show “Searching…” until you click the X button to clear it. In the when.js example, the first (and only) result is selected as expected.
The docs say that geocode() should return a Promise.<Array.<GeocoderResult>> – I would be very happy if native Promise were supported, but until y’all figure out what’s broken maybe at least update the docs to specify when() instead?
Ubuntu 16.04, Chromium 58.0.3029.110 (latest stable)
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
As of https://github.com/CesiumGS/cesium/pull/10149, I believe this is resolved. Let me know if I’m missing anything.
It’s in two places:
https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/Widgets/Geocoder/GeocoderViewModel.js#L348
and
https://github.com/AnalyticalGraphicsInc/cesium/blob/master/Source/Widgets/Geocoder/GeocoderViewModel.js#L446
I think that should fix the issue.