The issue I reported on Saturday has now been fixed in a hot-fix to 2018.2 it was defect 507448