Delete .github/workflows/release.yml #2175
Open
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
* fix: import rememberMarkerState and use the marker state correctly * feat: dataset styling Kotlin samples * feat: added DataDrivenBoundariesActivity.kt * feat: added DataDrivenBoundariesActivity * feat: added documentation * feat: added header * chore: changed MY_MAP_ID to DEMO_MAP_ID * feat: moved data files to raw * feat: added DataDrivenBoundariesActivity * feat: removed unused files * feat: map id * chore: replace System.out.println with Log.d * feat: added region tags * feat: added different set of DDS * feat: added different set of DDS * feat: replacing files feat: replacing files * feat: replacing files * feat: compileSdk 35 * feat: compileSdk 35 * chore: updated README file * feat: trying to force different datasets * feat: updated samples * feat: Add data-driven styling for datasets This commit introduces data-driven styling for datasets in the ApiDemos application. The following changes were made: Added a custom Application class (ApiDemoApplication) to check for the presence and validity of the API key during startup. Added a new data structure (DataSet) to hold information about each dataset, including its label, dataset ID, location, and styling callback. Updated the DataDrivenDatasetStylingActivity to use the new data structure and styling callbacks. Rename the dataset input files to better reflect there contents. * fix: moves the dataset ids to the secrets.properties file * feat: significant rewrite to of DataDrivenDatasetStylingActivity * Makes the app look better on full screen with a cutout * Uses material elements * Switch to using secrets for the data set ids * more of a convenience to prevent having to remove the ids when submitting * moves dataset data files to common area since they are not used directly by the app * Detailed instructions for uploading the data to console (WIP) * fix: exports the data driven styling activities so they can be run directly * feat: added header * feat: change ubuntu-latest * feat: change ubuntu-latest * feat: change ubuntu-latest --------- Co-authored-by: dkhawk <107309+dkhawk@users.noreply.github.com>
# [1.15.0](googlemaps-samples/android-samples@v1.14.0...v1.15.0) (2025-02-13) ### Features * Data-Driven styling samples ([googlemaps-samples#1771](googlemaps-samples#1771)) ([f4654e6](googlemaps-samples@f4654e6))
…y.java demo (googlemaps-samples#1979) * fix: support devices with cutouts for DataDrivenDatasetStylingActivity.java demo * fix: remove unnecessary 'res/' from paths in README.md file * feat(apidemos): enhance DataDrivenBoundariesActivity UI and boundary selection This commit enhances the DataDrivenBoundariesActivity demo with UI and functionality improvements focusing on boundary type selection and visual enhancements. - Implements Material Design theming and UI elements. - Adds boundary type selection via PopupMenu (Locality, Admin Area, Country). - Refactors styling and implements persistent country selection. - Handles system UI insets for improved display. These changes improve the demo's user experience and code structure, better showcasing data-driven boundary styling. * feat(apidemos): configure dataset-specific zoom levels for datasets demo This commit introduces dataset-specific zoom levels to the DataDrivenDatasetStylingActivity, enhancing the user experience when switching between datasets. - Adds a `zoomLevel` field to the `DataSet` class to store the desired zoom level for each dataset. - Updates the `dataSets` array to include appropriate zoom levels for Boulder, New York, and Kyoto datasets. - Modifies the `centerMapOnLocation` method to accept a `zoomLevel` parameter, allowing it to be dynamically set. - Updates the `switchDataSet` method to utilize the `zoomLevel` from the selected `DataSet` when centering the map, ensuring the map zooms to the optimal level for each dataset. - Removes the previously hardcoded `ZOOM_LEVEL` constant, as the zoom level is now dataset-dependent. These changes ensure that when a user selects a dataset, the map automatically zooms to a relevant level for that specific dataset, improving clarity and usability of the demo. Also adds missing copyright header.
## [1.15.1](googlemaps-samples/android-samples@v1.15.0...v1.15.1) (2025-02-14) ### Bug Fixes * support devices with cutouts for DataDrivenDatasetStylingActivity.java demo ([googlemaps-samples#1979](googlemaps-samples#1979)) ([683b21d](googlemaps-samples@683b21d))
* feat: added material to samples * feat: WIP * feat: added material to samples * feat: some more samples * feat: base activity * feat: some more samples
# [1.16.0](googlemaps-samples/android-samples@v1.15.1...v1.16.0) (2025-03-04) ### Features * added material to samples ([googlemaps-samples#1991](googlemaps-samples#1991)) ([78c0aed](googlemaps-samples@78c0aed))
* chore: update README per template * chore: more README fixes from template Skipping failed tests for this README update.
* chore: unified Kotlin and Java modules
* chore: unified resources
* chore: removed Kotlin
* chore: headers
* chore: headers
* chore: headers
* chore: headers
* chore: added insets
* chore: headers
* chore: renamed
* fix: Refactor map creation, centralize Map ID, add Kotlin boundary controls
This commit refactors how map fragments and Map IDs are handled across the Java and Kotlin demo applications, and introduces feature parity for boundary layer controls in the Kotlin demo.
Key changes include:
- **Programmatic Map Fragment Creation:**
- Replaced static `<fragment>` map declarations with `<FrameLayout>` containers (`map_fragment_container`) in `data_driven_boundaries_demo.xml` and `data_driven_styling_demo.xml` layouts.
- Modified `DataDrivenBoundariesActivity` and `DataDrivenDatasetStylingActivity` (Java & Kotlin) to instantiate `SupportMapFragment` programmatically using `SupportMapFragment.newInstance(mapOptions)`.
- Map options (`GoogleMapOptions`) are now created with the dynamically retrieved Map ID before fragment creation.
- this allows moving the Map ID out of the xml files
- **Centralized Map ID and Configuration Logic:**
- Introduced `ApiDemoApplication` in both Java (`java-app`) and Kotlin (`kotlin-app`) modules.
- This class centralizes Map ID retrieval, checking `BuildConfig.MAP_ID` first, then the `R.string.map_id` resource, providing a consistent source.
- The Kotlin `ApiDemoApplication` also includes API Key validation on application startup.
- **Kotlin DataDrivenBoundaries Feature Enhancement:**
- Added boundary layer selection controls (popup menu via `button_feature_type`) to the Kotlin `DataDrivenBoundariesActivity`, achieving parity with the Java version's functionality.
- Implemented state management for toggling Locality, Administrative Area Level 1, and Country layers.
- Added dynamic styling logic to apply/remove styles based on layer visibility.
- Updated feature click handling for country selection, respecting layer activation state.
- **Miscellaneous Improvements:**
- Added distinct demo titles (`demo_title_java`, `demo_title_kotlin`) in `strings.xml` for better app identification.
- Updated resource references within Java/Kotlin activities for cleaner imports (e.g., `R.id...` instead of fully qualified names).
* chore: address various lint issues
* fix: explicitly bind checkboxes in the UI
---------
Co-authored-by: dkhawk <107309+dkhawk@users.noreply.github.com>
* chore: updated versions * chore: updated snippets * chore: updated tutorials java * chore: updated tutorials java * chore: permission * chore: permission * chore: added material
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.
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕