Releases: MelihAltintas/vue3-openlayers
Releases · MelihAltintas/vue3-openlayers
Release 10.0.1
Release 10.0.0
10.0.0 (2024-05-22)
Bug Fixes
- update falsy values "0", "false" and "null" (b39d0c6)
Code Refactoring
- composables: rename composable
useLayerInMapOrLayerGroup
intouseLayer
(3a7835c) - ol-source-*: move common setup into
useSource
composable (56b386d), closes #354
Features
- ol-layer-*: support common events on components (69b37c9)
BREAKING CHANGES
- composables: The composable
useLayerInMapOrLayerGroup
was renamed touseLayer
- ol-source-*: The created Source class from the corresponding OpenLayers source isn't wrapped in a computed anymore but in a shallowRef. This will improve the performance and prevent unneeded re-computations.
Also, the providedimageLayer
references is now wrapped in aRef
which will make it reactive:
In case the layer changes, the source is updated and applied to the changed layers reference.
This behavior was already default for all layer types:-const layer = inject<ImageLayer<Static> | null>("imageLayer"); +const layer = inject<Ref<ImageLayer<Static>> | null>("imageLayer");
Release 9.0.3
Release 9.0.2
Release 9.0.1
Release 9.0.0
9.0.0 (2024-05-12)
Bug Fixes
- ol-overlay: set correct default values as described in the docs (2e9e2a6), closes #346
- ol-source-wmts: add missing optional
tileGrid
prop (1237fe1) - ol-vector-layer: watch opacity / visible changes (e9ae6fa), closes #347
Code Refactoring
- ol-layer-*: push layer to correct collection based on parent component injection (ee46969), closes #344 #344
BREAKING CHANGES
- ol-layer-*: These changes may not affect you directly. Previously, for some layer types, a layer was always added to the map, even if the layer component was used within a LayerGroup. This resulted in layers existing multiple times (in the LayerGroup and at the top level (Reported in #344)). Due to the refactoring, all layers are now treated the same (with onMounted and when changing layer properties).
1.) If the layer component is within anol-layer-group
, it is added to the group.
2.) If the layer component is inside anol-overviewmap-control
, it is added to the OverviewMap
3.) If 1) and 2) do not apply, the layer component is added directly to the map
Release 8.1.0
Release 8.0.0
8.0.0 (2024-04-18)
Code Refactoring
- rename components (ea85a6e)
Features
- support PascalCase component usage for global plugin installations (861f3ea)
BREAKING CHANGES
- Several components have been renamed. Adjustments are only necessary when not consuming these components as a plugin but directly. When using a plugin for global component availability, nothing has been changed. This change was necessary to align the names of directly importable and usable components with the global names provided by the plugins.
<Animations.OLAnimationDrop>
was renamed to<Animations.OlAnimationDrop>
<Interaction.OlClusterSelectInteraction>
was renamed to<Interaction.OlInteractionClusterselect>
<Interaction.OlDragBoxInteraction>
was renamed to<Interaction.OlInteractionDragbox>
<Interaction.OlDragRotateInteraction>
was renamed to<Interaction.OlInteractionDragrotate>
<Interaction.OlDragRotateZoomInteraction>
was renamed to<Interaction.OlInteractionDragrotatezoom>
<Interaction.OlLinktInteraction>
was renamed to<Interaction.OlInteractionLink>
<Interaction.OlSelectInteraction>
was renamed to<Interaction.OlInteractionSelect>
<Interaction.OlDrawInteraction>
was renamed to<Interaction.OlInteractionDraw>
<Interaction.OlModifyInteraction>
was renamed to<Interaction.OlInteractionModify>
<Interaction.OlSnapInteraction>
was renamed to<Interaction.OlInteractionSnap>
<Interaction.OlTransformInteraction>
was renamed to<Interaction.OlInteractionTransform>
<Layers.OlAnimatedClusterLayer>
was renamed to<Layers.OlAnimatedClusterlayer>
<Map.OlGeoLocation>
was renamed to<Map.OlGeolocation>
<MapControls.OlFullScreenControl>
was renamed to<MapControls.OlFullscreenControl>
<MapControls.OlMousePositionControl>
was renamed to<MapControls.OlMousepositionControl>
<MapControls.OlOverviewMapControl>
was renamed to<MapControls.OlOverviewmapControl>
<MapControls.OlScaleLineControl>
was renamed to<MapControls.OlScalelineControl>
<MapControls.OlZoomSliderControl>
was renamed to<MapControls.OlZoomsliderControl>
<MapControls.OlZoomToExtentControl>
was renamed to<MapControls.OlZoomtoextentControl>
<MapControls.OlPrintDialogControl>
was renamed to<MapControls.OlPrintdialogControl>
<MapControls.OlVideoRecorderControl>
was renamed to<MapControls.OlVideorecorderControl>
<MapControls.OlLayerSwitcherControl>
was renamed to<MapControls.OlLayerswitcherControl>
<MapControls.OlLayerSwitcherImageControl>
was renamed to<MapControls.OlLayerswitcherimageControl>
<Sources.OlSourceBingMaps>
was renamed to<Sources.OlSourceBingmaps>
<Sources.OlSourceImageWMS>
was renamed to<Sources.OlSourceImageWms>
<Sources.OlSourceOSM>
was renamed to<Sources.OlSourceOsm>
<Sources.OlSourceTileArcGISRest>
was renamed to<Sources.OlSourceTileArcgisRest>
<Sources.OlSourceGeoTIFF>
was renamed to<Sources.OlSourceGeoTiff>
<Sources.OlSourceTileJSON>
was renamed to<Sources.OlSourceTileJson>
<Sources.OlSourceTileWMS>
was renamed to<Sources.OlSourceTileWms>
<Sources.OlSourceXYZ>
was renamed to<Sources.OlSourceXyz>
<Sources.OlSourceWMTS>
was renamed to<Sources.OlSourceWmts>
Release 7.0.0
7.0.0 (2024-04-13)
Bug Fixes
- ol-*-control: make sure control is updated on property changes (507220d)
- ol-map: use correct typings for exposed function
forEachFeatureAtPixel
(8db77a0) - ol-webgl-vector-layer: pass internal
style
prop tostyles
(e3baa82)
chore
- set minimum peerDependency of OpenLayers to version 9.1.0 (77e022b)
- set minimum peerDependency of vue to version 3.4.15 (cc35ae8)
Code Refactoring
- ol-animation-feature: remove unused exported component
ol-animation-feature
(4190325)
Features
- allow to define global options for child plugins and via
provide
(55f4c1f)
Performance Improvements
- prevent watching reactive props continously (7e13440)
BREAKING CHANGES
- ol-animation-feature: The component
ol-animation-feature
was simply exposing the map, vectorLayer and it's passed properties. There was no need to use this component at all and therefore it has been removed. However, when the component was used in the past, make sure to remove it from your template and move theref
's for map and the layer to the correct components. - The minimum version of Vue is now 3.4.15 (
npm i vue@^3.4.15
) - The minimum version of OpenLayers is now 9.1.0 (
npm i ol@^9.1.0
) - the composable
usePropsAsObjectProperties
which is used as foundation in all components has been refactored.
Props were watched always deeply and for lot's of components this was done multiple times since the components implement watchers by themselves.
However, even if not expected, this may cause some side effects with reactive changes which must be applied for individual components when not implemented and therefore considered as a breaking change.
Please check your app carefully when updating to the new major version.
Release 7.0.0-1
7.0.0-1 (2024-04-12)
chore
- set minimum peerDependency of OpenLayers to version 9.1.0 (8ae195c)
- set minimum peerDependency of vue to version 3.4.15 (158f00e)
Code Refactoring
- ol-animation-feature: remove unused exported component
ol-animation-feature
(90f082a)
Performance Improvements
- prevent watching reactive props continously (45f9326)
BREAKING CHANGES
- ol-animation-feature: The component
ol-animation-feature
was simply exposing the map, vectorLayer and it's passed properties. There was no need to use this component at all and therefore it has been removed. However, when the component was used in the past, make sure to remove it from your template and move theref
's for map and the layer to the correct components. - The minimum version of Vue is now 3.4.15 (
npm i vue@^3.4.15
) - The minimum version of OpenLayers is now 9.1.0 (
npm i ol@^9.1.0
) - the composable
usePropsAsObjectProperties
which is used as foundation in all components has been refactored.
Props were watched always deeply and for lot's of components this was done multiple times since the components implement watchers by themselves.
However, even if not expected, this may cause some side effects with reactive changes which must be applied for individual components when not implemented and therefore considered as a breaking change.
Please check your app carefully when updating to the new major version.