RC #261 - Location markers #266
Merged
Conversation
This file contains 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
added 2 commits
March 11, 2024 20:08
…ort for multiple geometries; Adding "core_data" middleware
ajolipa
approved these changes
Mar 12, 2024
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 pull request renames the LocationMarker component to "LocationMarkers" and adds the
animateprop to allow for conditional map marker pulse to display. This pull request also renames the PlaceMarker component to "PlaceMarkers" and updates it to support multiple Core Data place URLs via theurlsprop. Finally, this pull request adds the/core_data/placesand/core_data/places/:idAPI endpoints to Storybook to provide test data in an attempt to remove all of the hard coded Core Data Staging URLs from stories.