-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Open
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem teamTriaged by Ecosystem team
Description
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:
maRci002, Reprevise, absar and PackRuble
Metadata
Metadata
Assignees
Labels
P2Important issues not at the top of the work listImportant issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.Team-specific productivity, code health, technical debt.packageflutter/packages repository. See also p: labels.flutter/packages repository. See also p: labels.team-ecosystemOwned by Ecosystem teamOwned by Ecosystem teamtriaged-ecosystemTriaged by Ecosystem teamTriaged by Ecosystem team