Skip to content

☂️ Align 1P plugin error handling with best practices #124800

@stuartmorgan-g

Description

@stuartmorgan-g

Our wiki documents our ideal error handling best practices, where we have a structured error system that's clearly defined as part of the API, rather than just having all the errors be PlatformExceptions that come directly from the native side and are frequently inconsistent and/or undocumented. However, almost all of our 1P plugins are currently doing the later since the guidance is recent, and we treat significant changes to errors as breaking changes, so can't fix them incrementally.

This is an umbrella for auditing each plugin and determining what changes we should make, then filing sub-issues to track each specific plugin's tasks.

Subtasks that have been filed so far:

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions