Update: Report assignment expression location in no-cond-assign #12465
Sorry, the PR description was confusing, that's exactly what this PR does - reports the 'invalid'
I agree there is no reason to report
One last question before we merge this - it looks like the consensus is to accept this as a bug fix. It seems to me like it should still be considered a semver-minor change because it can lead to more errors in the case described in the original description. Thoughts?