@datatitian I have seen discussion in the core dev team about removing that and either bringing back the old behavior or doing something different. so I am probably not going to touch it for now