Version Packages - #4
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@xtramaps/layer-control-maplibre@1.1.0
Minor Changes
@xtramaps/layer-control-maplibre(core) and@xtramaps/layer-control-maplibre-react: the LayerControl component extracted fromogcapi-html, supporting nested groups, radio-groups and merge-groups (includingsourceLayerauto-collection). Legend icons are now provided by@xtramaps/legend-symbols-maplibre-reactinstead of a local copy. Mounted via@vis.gl/react-maplibre'suseControl/useMapand composed explicitly as a child of@xtramaps/web-map-maplibre-react'sMapLibrecomponent (no dependency between the two packages).@xtramaps/web-map-cesium@1.1.0
Minor Changes
d80e22d: Add
@xtramaps/web-map-cesium(core) and@xtramaps/web-map-cesium-react: the Cesium map component migrated fromogcapi-html, onto current@cesium/engine/@cesium/widgets(^26/^16, up from^2.3.0/^2.2.0). Same viewer construction (background imagery, terrain), 3D Tileset loading (including the vertical-shift correction math), and no LayerControl/legend equivalent - the original never had one for Cesium either.Unlike the OpenLayers/MapLibre migrations, the original
Cesiumcomponent was never a React component - it was a single imperative function called once per page load, with no cleanup, no error handling on its async tileset/style loading, and two previously-dead CSS rules (style.csswas never imported).web-map-cesium-reactwraps the same logic in auseEffect-driven component and makes three deliberate additions the original didn't have, since a reusable library component can be mounted and unmounted repeatedly (Storybook, demos, consumer apps) unlike a one-shot page script:viewer.destroy()runs on unmountThe component mounts once; prop changes after the initial render aren't reflected, matching the original's single-mount design (Cesium never had a dynamic update path the way OpenLayers/MapLibre's TileMatrixSet switching does).
@xtramaps/web-map-maplibre@1.1.0
Minor Changes
@xtramaps/web-map-maplibre(core) and@xtramaps/web-map-maplibre-react: the MapLibre map component extracted fromogcapi-html, rebuilt on@vis.gl/react-maplibreand currentmaplibre-gl(^6) instead of the unmaintainedreact-maplibre-ui. Includes style/data-layer helpers, hover/click popups, and aCanvasOverlay(formerlyCanvasPlugin) for rendering arbitrary React children into the map canvas.@xtramaps/web-map-openlayers@1.1.0
Minor Changes
@xtramaps/web-map-openlayers(core) and@xtramaps/web-map-openlayers-react: the OpenLayers map component migrated 1:1 fromogcapi-html, onto currentrlayers(3.9.0) andol(10.8.0) instead of the outdatedrlayers@1.1.1/ol@6.9.0. Unlike the MapLibre extraction, this is a pure migration with no new LayerControl/legend equivalent — the original component never had one. TheglobalThis._map.setCurrentTileMatrixSetglobal bridge is replaced with aforwardRef/useImperativeHandle-based ref API.@xtramaps/layer-control-maplibre-react@1.1.0
Minor Changes
@xtramaps/layer-control-maplibre(core) and@xtramaps/layer-control-maplibre-react: the LayerControl component extracted fromogcapi-html, supporting nested groups, radio-groups and merge-groups (includingsourceLayerauto-collection). Legend icons are now provided by@xtramaps/legend-symbols-maplibre-reactinstead of a local copy. Mounted via@vis.gl/react-maplibre'suseControl/useMapand composed explicitly as a child of@xtramaps/web-map-maplibre-react'sMapLibrecomponent (no dependency between the two packages).Patch Changes
@xtramaps/web-map-cesium-react@1.1.0
Minor Changes
d80e22d: Add
@xtramaps/web-map-cesium(core) and@xtramaps/web-map-cesium-react: the Cesium map component migrated fromogcapi-html, onto current@cesium/engine/@cesium/widgets(^26/^16, up from^2.3.0/^2.2.0). Same viewer construction (background imagery, terrain), 3D Tileset loading (including the vertical-shift correction math), and no LayerControl/legend equivalent - the original never had one for Cesium either.Unlike the OpenLayers/MapLibre migrations, the original
Cesiumcomponent was never a React component - it was a single imperative function called once per page load, with no cleanup, no error handling on its async tileset/style loading, and two previously-dead CSS rules (style.csswas never imported).web-map-cesium-reactwraps the same logic in auseEffect-driven component and makes three deliberate additions the original didn't have, since a reusable library component can be mounted and unmounted repeatedly (Storybook, demos, consumer apps) unlike a one-shot page script:viewer.destroy()runs on unmountThe component mounts once; prop changes after the initial render aren't reflected, matching the original's single-mount design (Cesium never had a dynamic update path the way OpenLayers/MapLibre's TileMatrixSet switching does).
Patch Changes
@xtramaps/web-map-maplibre-react@1.1.0
Minor Changes
@xtramaps/web-map-maplibre(core) and@xtramaps/web-map-maplibre-react: the MapLibre map component extracted fromogcapi-html, rebuilt on@vis.gl/react-maplibreand currentmaplibre-gl(^6) instead of the unmaintainedreact-maplibre-ui. Includes style/data-layer helpers, hover/click popups, and aCanvasOverlay(formerlyCanvasPlugin) for rendering arbitrary React children into the map canvas.Patch Changes
@xtramaps/web-map-openlayers-react@1.1.0
Minor Changes
@xtramaps/web-map-openlayers(core) and@xtramaps/web-map-openlayers-react: the OpenLayers map component migrated 1:1 fromogcapi-html, onto currentrlayers(3.9.0) andol(10.8.0) instead of the outdatedrlayers@1.1.1/ol@6.9.0. Unlike the MapLibre extraction, this is a pure migration with no new LayerControl/legend equivalent — the original component never had one. TheglobalThis._map.setCurrentTileMatrixSetglobal bridge is replaced with aforwardRef/useImperativeHandle-based ref API.Patch Changes