fix: Check defined on RSpec.configure instead of RSpec #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📢 Type of change
📜 Description
Check defined on RSpec.configure instead of RSpec to avoid undefined method exception
💡 Motivation and Context
Issue happened on:
rspec-railsgem only and not depends onrspec-coredirectlydry-validation-matchersgem was defined afterrspec-railsgemIssue trigger:
rails crails s -b 0.0.0.0Error log when exception raised:
Analysis:
rspec-railsbehavior was extending RSpec module, that makes the RSpec module defined but theconfiguremethod was not defined (ref)Solution:
RSpec.configuredefined or not instead of checkingRSpec. This also makes the checking more relate with the execution insideif defined?block because it only call theconfiguremethodAlternative solution on this issue:
rspec-coreto the gemfile and defined it beforedry-validation-helperor
dry-validation-helpergem beforerspec-railsgem💚 How did you test it?
rake specresult:another testing methods:
rails crails s -b 0.0.0.0📝 Checklist