Then the biggest thing is resolving changes to peeks: ideally if you have a map peek whose contents update and the code yields a new value, it smoothly calls setGeoJSON() instead of rebuilding it from scratch. This means that peeks need to track position, previous content, current content, and preference for formatter.
Then the biggest thing is resolving changes to peeks: ideally if you have a map peek whose contents update and the code yields a new value, it smoothly calls setGeoJSON() instead of rebuilding it from scratch. This means that peeks need to track position, previous content, current content, and preference for formatter.