Naming/ConstantName flags conditional assignments of classes to camel-cased constants

[patbl]

Expected behavior

I expected this not to trigger the Naming/ConstantName cop:

class Foo; end
class Bar; end

Lol = if true then Foo else Bar end

The docs say

To avoid false positives, it ignores cases in which we cannot know for certain the type of value that would be assigned to a constant.

The changelog says

Fix false positive in Naming/ConstantName when using conditional assignment. (@Drenmi)

Actual behavior

That code triggered the Naming/ConstantName cop.

Steps to reproduce the problem

~  ➜ cat foo.rb
class Foo; end
class Bar; end

Lol = if true then Foo else Bar end
~  ➜ rubocop --only Naming/ConstantName foo.rb
Inspecting 1 file
C

Offenses:

foo.rb:4:1: C: Naming/ConstantName: Use SCREAMING_SNAKE_CASE for constants.
Lol = if true then Foo else Bar end
^^^

1 file inspected, 1 offense detected

This isn't a problem without the conditional:

~  ➜ cat bar.rb
class Foo; end
Bar = Foo
~  ➜ rubocop --only Naming/ConstantName bar.rb
Inspecting 1 file
.

1 file inspected, no offenses detected

RuboCop version

~  ➜ rubocop -V
0.58.1 (using Parser 2.5.1.0, running on ruby 2.5.1 x86_64-darwin17)