Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Running `stack config set resolver X` inside a project modifies the global project's stack.yaml #2709
This bug probably crept in during 0bdab6e.
I think I missed that the
I probably won't get around to fixing this until Sunday…
I also think that it would be good to have safeguards against bugs like this, for example by assigning different types to
Well, I assume I was using some dev version of stack, that I had built while working on 0bdab6e.
I guess I confused
Consequently closing as "false alarm". If anyone else can reproduce the issue, please reopen.
This bug has popped up again:
I guess this is a side effect of d0eabec.
Thanks for taking care of this but I don't think your fix works at intended.
In particular I can't figure out how to apply that
I'm also not convinced that the
There's also a this debug print statement that should be removed.
Oh yeah, I realize that I am now myself confused about the "global project" and the
I really think we need a better terminology here.
Maybe call the
Looks good now!
I think it's a bad sign that this issue confuses even the developers, so IMHO the sooner this issue is fixed, the better. I still assume that