Open GoogleCodeExporter opened 9 years ago
Patches gladly accepted :-)
Original comment by sberlin
on 5 Dec 2013 at 10:43
I was going to cook something up, but I just realised that you can't handle
multiple nested modules that should all be skipped. The inner module doesn't
know that the outer one is skipped too.
Another solution is to delay computing the skipped sources until later.
Element.applyTo() would still call binder.withSource(), but pass it the whole
stack trace instead of just the top element. The binder would go through the
stack trace until it found an element that wasn't skipped.
But that's a huge change for a reasonably corner case. I'm open to other
suggestions.
Original comment by tavianator@gmail.com
on 6 Dec 2013 at 11:51
Original issue reported on code.google.com by
tavianator@gmail.com
on 7 Oct 2013 at 6:04