Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

Preliminary status command #8

Merged
merged 11 commits into from
Oct 25, 2016
Merged

Preliminary status command #8

merged 11 commits into from
Oct 25, 2016

Conversation

sdboyer
Copy link
Member

@sdboyer sdboyer commented Oct 18, 2016

This is a preliminary implementation of a status command. (It includes everything in #7, and supercedes it so i'm closing that PR), but does kinda sorta the basics. Or could. Right now, it basically just does the setup :)

This is the minimum amount necessary to get a SourceManager working.
Mostly just a helper function that pulls together the basic info we need
for most commands.
This is hardly complete, particularly given the empty
collectConstraints() func and the fact that our manifests and locks
don't really support working with actual code yet. Nevertheless, it is
at least a strong demonstration of how one goes about collecting the
relevant information.
@freeformz
Copy link

Aside from my one comment, just 👍 this and merge it. We can revisit later IMO.


type project struct {
root string
pr gps.ProjectRoot

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is a root (string) and a projectRoot ? What makes them different?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, i should name the vars better so that it's clearer.

root is a string that describes the absolute path to the root of the repository. a ProjectRoot, istype ProjectRoot string, but is specifically intended to be an import path that corresponds to the root of a project/repository.

I'm not entirely happy with doing things this way, but as the linked docs note, I did it because being clear about when a string is expected to have the specific properties of being a root project import path, vs just an fs path, vs any import path, are so muddled in a lot of this domain that i wanted a stronger signaling mechanism to implementors about when we needed this type of thing in particular.

@sdboyer
Copy link
Member Author

sdboyer commented Oct 21, 2016

hmm. i pushed some new commits, but during a github availability flap...it appears to have missed out on picking them up and showing them here, even though they're in the repo

@sdboyer
Copy link
Member Author

sdboyer commented Oct 21, 2016

nvm, there they are, didn't show until i commented. weird.

make lint most happy
@sdboyer sdboyer merged commit 4eb9342 into golang:master Oct 25, 2016
zbintliff added a commit to zbintliff/dep that referenced this pull request Mar 3, 2017
ibrasho pushed a commit to ibrasho-forks/dep that referenced this pull request May 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants