docs: Update import instructions in user guide #77
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rvl
force-pushed
the
rvl/user-guide-fixes
branch
from
f85a8af to
a3c51fa
Compare
|
The lack of comment constructors in |
angerman
approved these changes
Feb 28, 2019
There was a problem hiding this comment.
This looks good. With input-output-hk/nix-tools#31, we should have plan-to-nix which is almost identical to stack-to-nix in usage. There is also haskell.mkProjectPkgSet I think.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should make the user guide consistent with how hackage and stackage are imported.
The ascii box diagram still needs to be updated.
There is too much boilerplate in the docs. The tools should generate template files with comments explaining pinning, etc.