Skip to content

Replace most GoogleMap() rememberUpdatedState() usages with single State object and encapsulate Subcomposition functionality #492

@bubenheimer

Description

@bubenheimer

The GoogleMap() implementation uses a gazillion individual rememberUpdatedState() calls. This is unwieldy and likely contributed to #481.

Instead, a single State object encapsulating the individual state properties can be used and passed as a parameter. This pattern is in compliance with Google Compose API guidelines.

The subcomposition should be made a separate composable function to prevent accidental access to local variables and better encapsulate subcomposition functionality.

Metadata

Metadata

Assignees

No one assigned

    Labels

    triage meI really want to be triaged.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions