The docs link that refers to the new .with(...) method is leading to a wrong place in the documentation, that should be fixed