Conversation

emptyflask

I ran into a bunch of warnings when using Elastic results with
Ruby 2.4+ and trailblazer/cells, because #method_missing? without
#respond_to_missing? makes Forwardable think all of the Result
attributes are private methods.

https://robots.thoughtbot.com/always-define-respond-to-missing-when-overriding

I ran into a bunch of warnings when using Elastic results with
Ruby 2.4+ and trailblazer/cells, because `#method_missing?` without
`#respond_to_missing?` makes Forwardable think all of the Result
attributes are private methods.

https://robots.thoughtbot.com/always-define-respond-to-missing-when-overriding
@emptyflask

Apologies to @nutsoriginal, I didn't see his PR (#727) until opening this one. Anyway, this has some test coverage.

@emptyflaskemptyflask changed the title respond_to_missing? to silence Ruby 2.4 warnings [MODEL]respond_to_missing? to silence Ruby 2.4 warnings Sep 18, 2018
@emptyflask

I've signed the CLA.

@estolfo

Thanks @emptyflask and @nutsoriginal

@estolfoestolfo merged commit 3f2c03f into elastic:master Oct 17, 2018
estolfo pushed a commit that referenced this pull request Oct 17, 2018
I ran into a bunch of warnings when using Elastic results with
Ruby 2.4+ and trailblazer/cells, because `#method_missing?` without
`#respond_to_missing?` makes Forwardable think all of the Result
attributes are private methods.

https://robots.thoughtbot.com/always-define-respond-to-missing-when-overriding
@emptyflaskemptyflask deleted the fix/respond_to branch April 24, 2019 14:08
vanboom added a commit to vanboom/elasticsearch-rails that referenced this pull request Nov 10, 2023
…nt, fix index name to klass lookup methodology
vanboom added a commit to vanboom/elasticsearch-rails that referenced this pull request Nov 11, 2023
Sign up for free to join this conversation on . Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.