-
Notifications
You must be signed in to change notification settings - Fork 1.7k
If a git path in a pubspec is relative interpret it relative to the pubspec #8570
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
Comments
Added Community-StarterBug label. |
Removed this from the Later milestone. |
Removed Oldschool-Milestone-Later label. |
This comment was originally written by @kaendfinger Shouldn't this have a PatchesWelcome label? |
Patches are welcome on every bug! :) I think the "PatchesWelcome" usually means "we don't intend to put time into this ourselves, but will take a contribution from someone else for it", but I'm not positive since I haven't used that tag. |
Well, let me qualify that by saying contributions are welcome on every bug, but we do like to know a bit about what the contributor has in mind before seeing an actual patch. We don't always do a great job of writing down the full context behind some bug, so there may be some tribal knowledge to impart before a contributor gets coding. |
This issue has been moved to dart-lang/pub#449. |
You can use a file path as a git dependency. When you do, it's interpreted as relative to the package directory of the root package. It should be resolve as relative to the pubspec that contains the dependency (like relative path deps are).
The text was updated successfully, but these errors were encountered: