-
Notifications
You must be signed in to change notification settings - Fork 519
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
Replace lockfile format with JSON? #53
Comments
actually I'm very happy with format. It's exactly the same as bundler |
/cc @agross |
I have to admit I like the readability of the current format. Simple, no distractions like braces to satisfy a tool. AlexAlexander Groß On Thu, Sep 4, 2014 at 7:03 PM, Steffen Forkmann notifications@github.com
|
Yeah, true - my thinking is more around whether this is file designed to be read / written by people first and foremost (as is the case with the packages.fsx) or by Paket.exe? If the former - definitely makes sense to keep as is. If the latter - maybe not. |
It's meant to be read by people. You will always cross check before commit.
|
👍, I read it all the time to reason about paket's computation results. |
Closing :-) |
@forki Question - if the whole point of paket is to abstract users away from uber dependency chains - why would you cross check before commit? |
We want to make it super clear for the user to see what happens in his
|
We can simplify the code for reading and writing of the lockfile if we create a lockfile record and just use Newtonsoft JSON to handle the serialization (since v6 it has native support for F#).
The text was updated successfully, but these errors were encountered: