Yes, it’s a good improvement for sure. Something more "human readable" ;)
> Le 6 mai 2020 à 07:45, Steinar Bang <s...@dod.no> a écrit : > >>>>>> Łukasz Dywicki <l...@code-house.org>: > >> On the resolver thingy. >> I believe that the main problem we need to address is a format of error >> messages spit from our code. >> In quite many cases error takes half of the screen. Failure reason is at >> the end. Going over spaghetti causation in between is a challenge. > >> Making that readable in a tree form like below can make it simpler to >> read, easier to understand, making developer solve the problem faster. > >> ``` >> Failed to complete provisioning operation, here is a reason: >> - Resolution of feature X failed, because: >> - Resolution of feature Y failed, because: >> - Resolution of feature Z failed, because: >> - Resolution of bundle A failed, because: >> - Missing requirement 1-2-3 >> ``` > > +1 (non-binding) > > I would love to see something like this. >
