c4c73e05f5
## Motivation and Context The gemspec already declares `required_ruby_version >= 2.7.0`, but `ServerContext` used the `...` arguments forwarding syntax in `method_missing`. That syntax was added in Ruby 2.7.3, so requiring the gem raised a `SyntaxError` on Ruby 2.7.0 through 2.7.2, and the library could not be loaded at all. RuboCop did not catch this because its Parser backend runs on Ruby 2.7.8, where the syntax is valid. CI missed it too because the test matrix tested `2.7`, which resolves to the latest 2.7.x rather than the declared minimum. ## How Has This Been Tested? Forward arguments explicitly with `*args, **kwargs, &block` so the method loads on Ruby 2.7.0, and pin the CI test matrix to 2.7.0 so the suite runs against the declared minimum instead of the latest 2.7.x. Running the suite on 2.7.0 also requires a `Hash.ruby2_keywords_hash?` shim in the test helper, since mocha would otherwise raise a `NoMethodError` on that version. ## Breaking Changes None. Closes #418
24 lines
744 B
Ruby
24 lines
744 B
Ruby
# frozen_string_literal: true
|
|
|
|
require "mcp"
|
|
|
|
require "minitest/autorun"
|
|
require "minitest/mock"
|
|
require "mocha/minitest"
|
|
|
|
# mocha relies on `Hash.ruby2_keywords_hash?`, which is absent on Ruby 2.7.0 and the earlier 2.7.x releases
|
|
# before it was backported. Those versions also lack the flag-setting APIs, so no hash is ever flagged as
|
|
# ruby2_keywords and returning `false` is correct. Without this shim, mocha raises `NoMethodError` and
|
|
# the suite cannot run on Ruby 2.7.0.
|
|
unless Hash.respond_to?(:ruby2_keywords_hash?)
|
|
def Hash.ruby2_keywords_hash?(_hash)
|
|
false
|
|
end
|
|
end
|
|
|
|
require "active_support"
|
|
require "active_support/test_case"
|
|
|
|
require "sorbet-runtime" if RUBY_VERSION >= "3.0"
|
|
|
|
require_relative "instrumentation_test_helper"
|