Good news! We'll have a fix for this in the next release, v2.2 :)