You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
Once #470 gets merged, -gopath flag should be added to init to enable different modes of operations.
By default, init should operate in network mode. Passing -gopath should run init in existing mode (current behavior), scan through current GOPATH for on-disk projects. More details in the spec.
The text was updated successfully, but these errors were encountered:
Spent some time pondering and implementing and came up with 2 solutions. Need feedback on them.
In init, after getProjectData is run, if -gopath is not passed (Network mode), empty pd.constraints, move pd.ondisk elements to pd.notondisk and empty pd.ondisk. This approach is simple, but it contains fetching projectData, which does a lot of things.
Other approach would be to not fetch projectData and initialize empty manifest and lock. Run solver and populate manifest and lock from the solution. This approach requires some extra conditional code but less execution overhead.
I have tried both of them and results seem to be the same. I would like to know if not relying on projectData from getProjectData could have any side effects that I have overlooked.
Once #470 gets merged,
-gopath
flag should be added to init to enable different modes of operations.By default, init should operate in network mode. Passing
-gopath
should run init in existing mode (current behavior), scan through current GOPATH for on-disk projects. More details in the spec.The text was updated successfully, but these errors were encountered: