Thanks, this is now fixed and the correction will be available in next release 19.11 (and in next beta release 19.09)