![]() Custom MapController classes will stop working.Remove transition interpolator classes and use native methods such as Map.flyTo and Map.easeTo.We can add a stateful version of MapGL that renders fully asynchronously without any performance impact.3rd-party Mapbox addons will be supported by default.This will allow users to use the latest rendering and interactive options when they are released by Mapbox.Instead, we will pursue exposing mapbox-gl's native event system and attempt to hijack the camera change under the hood. Drop the usage of mjolnir.js' EventManager and subsequently MapController altogether.Make mapbox-gl a peer dependency so that the library is impartial about the version/fork used.This RFC is gathering feedback for the following major breaking changes proposed for react-map-gl v7. Considering the complexity of the task, it is unlikely for the current release to support Mapbox's non-WebMercator projection feature in its current state. The code base is quite complex already, with few developers able to navigate and contribute. #569, mapbox/mapbox-gl-js#3746, #725) and continues to generate hard-to-resolve feature requests ( #574, #1640, #1353, #775) and performance issues ( #1151, #909).ĭespite major efforts to improve the usability of the custom controller, it still has many open issues. This is arguably the one most controversial design decision of this project, dated back to before the current maintainers were involved. React-map-gl disables mapbox-gl's native event handling and implements its own. It has become increasingly difficult to maintain as Maplibre and Mapbox start making more aggressive breaking changes. The divergence happened when Mapbox changed its license, see #1380. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |