Repository navigation
Move submodules after the zIndex and projected-coordinate merges - #60
Merged
Merged
Conversation
…merges js-sdk-core 1de30fa..f4e5993 react-for-arcgis 0209db3..e3be428 react-for-azuremaps febadc6..a55b7c0 react-for-cesium 8bc6f77..f8670f1 react-for-deckgl e926803..2818400 react-for-googlemaps a1088ef..08945bc react-for-here 2d50ada..6f63b8c react-for-leaflet 7a71dea..8c21f99 react-for-longdo 7d3e698..de014d1 react-for-mapbox 51ee44a..9dc2d42 react-for-mapkit 4ce9305..efc85d9 react-for-maplibre 385b306..55c4aaf react-for-mappls 050084c..1611bc5 react-for-maptiler 774f77f..a0bb567 react-for-openlayers 9dd41c3..1450606 react-for-tomtom a274470..115ea9c
Includes MapCameraPosition.fov / paddings and the ArcGIS and Leaflet tilt fixes.
js-sdk-core and js-sdk-react are 0.4.0 now, so the in-repo templates ask for ^0.4.0 (their code already uses 0.4.0 exports such as circleMutations) and package-lock.json records the published 0.3.x copies the reactnative-for-* packages still resolve to. npm ci, npm test, npm run lint and the API surface check pass.
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.
Summary
Move the submodule pointers that received the marker zIndex ordering and projected-coordinate PRs to their current
develop, so the sample pages (Projected Coordinates) build against the merged APIs.js-sdk-core1de30fa..f4e5993react-for-arcgis0209db3..e3be428react-for-azuremapsfebadc6..a55b7c0react-for-cesium8bc6f77..f8670f1react-for-deckgle926803..2818400react-for-googlemapsa1088ef..08945bcreact-for-here2d50ada..6f63b8creact-for-leaflet7a71dea..8c21f99react-for-longdo7d3e698..de014d1react-for-mapbox51ee44a..9dc2d42react-for-mapkit4ce9305..efc85d9react-for-maplibre71c8df2..4a022a4 (55c4aaf plus the tile-warning commit from Log a tile that failed to load as a warning react-for-maplibre#37, so Bump react-for-maplibre: tile load failures as warnings #61's change is kept; its develop tip 873f741 also readsMapCameraPosition.fov, which js-sdk-core f4e5993 does not have yet)react-for-mappls050084c..1611bc5react-for-maptiler774f77f..a0bb567react-for-openlayers9dd41c3..1450606react-for-tomtoma274470..115ea9cOther submodules are left where they are.