resolves #7195
I recreated my branch from neomjs/neo and I think I've got my commit history reassembled cleanly so that it can merge successfully.
These commits:
-Delete OpenLayers.mjs since I chose to rename it to OpenStreetMaps.mjs. I think Open Streetmaps should be more recognizable to people compared to OpenLayers even though the library that's being leveraged is technically named OpenLayers.
-Added an example component and wrapper component for the addon to use for testing.
-Implemented create() and panTo() methods to get the example component to a minimum level of functionality including displaying a map, zooming, and panning between Iceland and San Francisco using the dedicated buttons.
Please make sure to read the Contributing Guidelines:
https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
If adding a new feature, the PR's description includes:
Other information:
resolves #7195 I recreated my branch from neomjs/neo and I think I've got my commit history reassembled cleanly so that it can merge successfully.
These commits: -Delete OpenLayers.mjs since I chose to rename it to OpenStreetMaps.mjs. I think Open Streetmaps should be more recognizable to people compared to OpenLayers even though the library that's being leveraged is technically named OpenLayers. -Added an example component and wrapper component for the addon to use for testing. -Implemented create() and panTo() methods to get the example component to a minimum level of functionality including displaying a map, zooming, and panning between Iceland and San Francisco using the dedicated buttons.
Please make sure to read the Contributing Guidelines:
https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch, not themainbranchfix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: