Open dolezvo1 opened 2 months ago
Yes we know and we faced this (suboptimal) design. It is bad. This behavior is a legacy. Can you tell us on which version of Pharo you are experiencing it?
Can you also provide a little case showing your problem so that we can use it to see how to fix it.
I've been trying to update an older project to work with newer codebase. During the install, I got the following warning/error:
That is to be expected, but the issue is that this warning/error does not (as far as I can tell) provide any information about the individual errors in the given definitions, which is very unhelpful for someone trying to fix those errors.
There is a variable called
errorDefinitions
which contains the definitions mentioned in the message above, but no trace of the exact errors.