Skip to content

Suggestion: Move location fetching logic out of KrossMapState #4

@amirroid

Description

@amirroid

Hi, thanks for the great work on KrossMap

I have a suggestion regarding how user location is handled. The logic for fetching the user's location currently resides in the KrossMapState class, which is mainly responsible for managing UI state. From a logical and architectural point of view, it might be better to move this functionality to a separate class to keep responsibilities well-separated.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions