Skip to content
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

Fix: shard.lock is always overwritten even when dependencies are up to date #370

Merged
merged 2 commits into from
Apr 30, 2020

Conversation

waj
Copy link
Member

@waj waj commented Apr 29, 2020

Since #354 unchanged locks are undetected and always overwritten after the "install" command

@waj waj force-pushed the fix/shard-lock-overwrite branch from b24a7d9 to a63f13d Compare April 29, 2020 21:49
Copy link
Member

@straight-shoota straight-shoota left a comment

Choose a reason for hiding this comment

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

There's surely a more efficient way than map, to_h and compare. Might not be super relevant here, but the code just looks quite off with so many transformations just to tell whether the locked versions match. Maybe sort + zip compare could be a better alternative?

@asterite
Copy link
Member

map block to_h is simply to_h block

@waj
Copy link
Member Author

waj commented Apr 30, 2020

@asterite is a little bit rude (and intimidating) to read the mind of others

@waj waj merged commit 5666481 into crystal-lang:master Apr 30, 2020
@waj waj deleted the fix/shard-lock-overwrite branch April 30, 2020 02:01
@asterite
Copy link
Member

:-)

Sorry for the brevity, cellphone

@bcardiff bcardiff added this to the v0.11.0 milestone May 27, 2020
taylor pushed a commit to vulk/shards that referenced this pull request Aug 11, 2020
f-fr pushed a commit to f-fr/shards that referenced this pull request Jan 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants