Skip to content

Clarify relationship between Description and ResolvedDescription #4579

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 15, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions lib/src/source.dart
Original file line number Diff line number Diff line change
Expand Up @@ -177,11 +177,17 @@ abstract class Source {
///
/// For a hosted package this would be the host url.
///
/// For a git package this would be the repo url and a ref and a path inside
/// the repo.
/// For a git package this would be the repo url and a ref and a path inside the
/// repo.
///
/// For a path package it is the path.
///
/// This is the information that goes into a `pubspec.yaml` dependency together
/// with a version constraint.
///
/// After resolution we might know more about the specifics of the package that
/// pins the content down (such as its content-hash or git commit id) this is
/// represented by a [ResolvedDescription].
abstract class Description {
Source get source;

Expand Down