@User thanks for the detailed bug report! i've recently ran into this myself and will be addressing this for the next release!