Skip to content

Support really large repos better #162

@thomasvl

Description

@thomasvl

This has come up in a few other issues, but addressing it seems to be non trivial. The main pain points:

  • The treeview starts by doing a query for all packages recursively. It would be nice if there was a way to do this progressively (like it does for targets within a package), but there doesn't seem to be a way to limit the depth of the package query.
  • There is no sharing of data between the treeview and quickpicks. If there was some "model" behind the scenes, then the quickpicks wouldn't have to issue queries if the model already had the data. There are a few complications though:
    • The treeview can progressively load targets as the tree is expanded, but for the quickpicks, that doesn't work as well, so the quickpicks would need some decisions about how to let the users progressively expand things.
    • Once data starts to be cached, how do things "refresh" when BUILD files are edited/added?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions