Skip to content

Centralize all checks for .packages and pubspec.yaml #4738

Open
@jacob314

Description

@jacob314

Bazel projects do not use pubspec.yaml or .packages files so all checks for pubspec.yaml and .packages need to be carefully audited to make sure we aren't breaking bazel support. We should define a PackageInfo class with a custom implementation for Bazel projects that wraps all cases where we need to perform logic that checks for pubspec.yaml, .packages with solutions that are appropriate under Bazel as well.

Activity

added this to the Backlog milestone on Aug 5, 2020
alexander-doroshko

alexander-doroshko commented on Aug 26, 2020

@alexander-doroshko
Contributor

Please keep me updated about the progress. We'll probably need to add the same changes to the Dart plugin. We need to be sure that the Flutter and Dart plugins agree which one is responsible for the pub actions bar in the pubspec file, which 'Outdated Dependencies' inspection should work, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @pq@jacob314@alexander-doroshko

        Issue actions

          Centralize all checks for .packages and pubspec.yaml · Issue #4738 · flutter/flutter-intellij