Lint/DuplicateBranch: bad behavior with pattern matching about rubocop HOT 4 CLOSED

Researched more and found out just need prefix _
https://womanonrails.com/ruby-pattern-matching-second-look (point 5)

So this works

# frozen_string_literal: true

require "httpx"

def handle_response(res)
  puts res.inspect
  case res
  in {status: 300...} | {error: _err}
    $stdout.puts "hi"
    puts "Error: #{_err}" if _err
  else
    $stdout.puts "bye"
  end
end

handle_response(HTTPX.get("https://exampleasdadadadad.org"))
handle_response(HTTPX.get("https://nginx.org"))
handle_response(HTTPX.get("https://reddit.com"))

from rubocop.

Even though it's in {error: error} that's highlighted, what the cop reports here is that you have $stdout.puts "hi" in two branches. The problem goes away if you change one of them to $stdout.puts "hello" for example.

from rubocop.

What I want to achieve is to $stdout.puts "hi" for both {status: 300...} & {error: error}
How should that be done?

from rubocop.

Warning: I'm not an expert in these matters. I've never used the pattern matching case..in construct myself and had to look it up.

Anyway, it seems like you can list several patterns by putting a | delimiter between them. It is, however, a syntax error to use variables like error in such expressions as it would not have a defined value in case of not matching. So:

def handle(res)
  case res
  in {status: 300...} | {error: _}
    $stdout.puts "hi", res
  else
    $stdout.puts "bye"
  end
end

handle(status: 300)
handle(error: 'Bad gateway')

will output

hi
{:status=>300}
hi
{:error=>"Bad gateway"}

Source: https://www.toptal.com/ruby/ruby-pattern-matching-tutorial

from rubocop.