Expose MapInstanceManager and the default projection settings at window.farmOS.map #122
Conversation
…ow.farmOS.map farmOS#122 **Why?** Make usage via `import` statements more consistent with the simple browser usage and enable externalizing to `window.farmOS.map`.
|
@jgaehring I'd love your thoughts on how well the changes here and in #117 have addressed the concerns you previously voiced about how farmOS-map is packaged and (with 1.x) needed to be consumed via |
|
So happy to see this going forward, @symbioquine! 👏 I think I need dedicate some time to getting up to speed on what's been done here and in #117 before I can meaningfully weigh in. I'm putting aside some time tomorrow afternoon to do so. I'll post back here with my initial thoughts after that and perhaps we can follow up in the monthly call this Wed, if you can make it, or some other time. |
|
Thanks @jgaehring! That sounds great, I should be on the Wednesday call. |
|
Oh this looks great, @symbioquine! I'm just about at the point where I can try this out in Field Kit this week or next, but from what I can tell looking at the diffs, this is a huge improvement. So glad you're giving this project the attention it needs! |
|
👍 @symbioquine @jgaehring and myself just discussed and agreed to merge this in to the 2.x branch. Then we can tag a 2.0.0 alpha release which will unblock next steps in #115 |
Why? Make usage via
importstatements more consistent with the simple browser usage and enable externalizing towindow.farmOS.map.