Make richer version conflict messages possible

[segiddins]

\c @indirect

[indirect]

👍

[alloy]

Nice 👍

[segiddins]

I'm kinda tempted to use this and make the tree-style output Bundler uses a builtin method on VersionConflict, something like tree_message. How does that sound?

[indirect]

I'm for it, but I designed the Bundler output. 😅

[alloy]

Just to be clear we’re on the same page, can you provide examples of the output?

[segiddins]

Bundler could not find compatible versions for gem "railties":
  In Gemfile:
    jquery-rails, resolved to 4.0.4 depends on
      railties (>= 4.2.0)

    rails-i18n, resolved to 4.0.4 depends on
      railties (~> 5.0)

    rails, resolved to 5.0.0.alpha depends on
      railties (= 5.0.0.alpha)

    codemirror-rails (= 4.2), resolved to 4.2 depends on
      railties (< 5, >= 3.0)

    rspec-rails (~> 2.14.0), resolved to 2.14.2 depends on
      railties (>= 3.0)

Could not find gem 'railties (~> 5.0)', which is required by gem 'jquery-rails', in any of the sources.

[segiddins]

(The code that generates that is pretty much https://github.com/bundler/bundler/blob/master/lib/bundler/resolver.rb#L13-L68)

[alloy]

Ok cool, yeah I like this message 👍

I’m less a fan of repeating the name of the dependency (railties) over and over, but maybe there’s a reason for that?

[segiddins]

@alloy reason for the repeated name is specific to this example, where lots of things had dependencies on railties. Note, I'm not suggesting making this format the default (because it requires a few parameters from the user), but I do think building it in would be nice.

[alloy]

Gotcha. I think it’s a good idea, do it 👍