Nick Sutterer
Nick Sutterer
Your autoloader is confused because you're not following the conventions somewhere, see https://trailblazer.to/2.1/docs/trailblazer.html#trailblazer-rails :wink:
We might need @solnic's help, then. It looks as if the class instance variables bleed through even after the reload.
@nicolaep Is `dry-system` doing the reloading?
This looks odd! Can you manually invoke `Trailblazer::Loader` with debugging on? https://github.com/trailblazer/trailblazer-loader#debugging
You're very smart, I like that! The loader code is super simplistic, maybe you can have a look yourself? It must be here: https://github.com/trailblazer/trailblazer-loader/blob/master/lib/trailblazer/loader.rb#L62
So when you run it in a real project, the sorting works different than in the test? Then, our algorithm must be flawed? :baby_chick: Are you 100% sure the same...
This is planned, yes. Why do you use exceptions? They are very hard to handle and take away flexibility you get from the pipe?
Yeah, that looks good to me, even though we will have an unlimited number of tracks in the next version, so we might have to use something like ```ruby [...
BTW, can I see some pseudo-code of how you'd use this on the outside, pleeheease?
@mensfeld Very simple, `Left` subclasses are always not successful and vice-versa for `Right`s, which means they are good. For now, I would suggest we only support an invisible third left...