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

Redirects/References Move Too Frequently #2228

Closed
BlythMeister opened this issue Apr 11, 2017 · 8 comments
Closed

Redirects/References Move Too Frequently #2228

BlythMeister opened this issue Apr 11, 2017 · 8 comments

Comments

@BlythMeister
Copy link
Contributor

It seems that the ordering of redirects and references changes very frequently.

Just recently with the release of 4.1.0 the binding redirect order changed.
every time this happens and we update paket, we get hundreds of file changes which make merges harder and merge conflicts higher.

An example of this move is:
image

@forki
Copy link
Member

forki commented Apr 11, 2017

yes I wondered too. I thought we order alphabetical. but something is fucky /cc @isaacabraham
I'm definetly interested in a fix that settles this

@RustyF
Copy link

RustyF commented Apr 18, 2017

(newbie alert). I'm trying to find something to fix but it looks like commit 3d0d8c5 fixes it? If so, what's the strategy for finding stuff actually not fixed (but not closed)?

@forki
Copy link
Member

forki commented Apr 18, 2017

I think we're missing a repro here. I don't know if it's fixed.

@BlythMeister
Copy link
Contributor Author

Unfortunately it's on a private repo, I guess create a project with the references on the before and after versions?

@cloudRoutine cloudRoutine added this to Current Feature Enhancements in paket-netcore Apr 19, 2017
@cloudRoutine cloudRoutine moved this from Current Feature Enhancements to Existing Feature Bugs in paket-netcore Apr 19, 2017
@RustyF
Copy link

RustyF commented Apr 19, 2017

I can reproduce it with a simple project. I will retrospectively add a test to thus cover #2230

@fsoikin
Copy link
Contributor

fsoikin commented Jul 2, 2017

So this issue should be closed now, right?

@BlythMeister
Copy link
Contributor Author

BlythMeister commented Jul 2, 2017

Yeah, the original issue is resolved now.

Though need a maintainer to close issue.

@forki
Copy link
Member

forki commented Jul 2, 2017

Thanks everyone

@forki forki closed this as completed Jul 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
paket-netcore
Existing Feature Bugs
Development

No branches or pull requests

4 participants