I think I just made a mistake there, that causes the error, this variation should remove that.
This does not work as a custom code snippet unfortunately. But I think this is going to be a permanent change in the upcoming release, so you don’t have to worry about it.