You can do `reflection.options.keys.include?(:inverse_of) && !reflection.options[:inverse_of]` so passing either explicit `nil` or `false` would work. I agree with original review that `nil` is more intuitive since it makes the line semantics more declarative (e.g. as a Rails developer I say there is 'no' defined inverse, rather than explicitly saying 'do not run some process that sets it'.