Skip to content

API conformance check has problems with nullable types #107035

@ueman

Description

@ueman

The API conformance check didn't caught the divergance of the API which was fixed in this PR flutter/engine#34428. Originally this divergance was submitted in flutter/engine#32078.
A possible cause could be due to the check not knowing about null-safe code.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority issues at the top of the work lista: null-safetySupport for Dart's null safety featureengineflutter/engine related. See also e: labels.platform-webWeb applications specificallyr: fixedIssue is closed as already fixed in a newer version

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions