This should be fixed for the 5.0 release and the documentation updated as well as mention in the 5.0 migration guide.