So it seems like we had something else in our codebase breaking this behaviour (which is actually default). Fixed!
