Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.13: lookup given hash_key: when possible #4286

Merged
merged 1 commit into from Jan 10, 2023
Merged

Conversation

rmosolgo
Copy link
Owner

Fixes #4072 (comment)

When a field is configured with hash_key:, look up that key using [...], even if the underlying object isn't a Hash. (This code checks for .respond_to?(:[]) to avoid breaking changes, which might be possible because of how hash_key was previously merged into method_* attributes.)

@rmosolgo rmosolgo added this to the 1.13.18 milestone Jan 10, 2023
@alexcwatt
Copy link

@rmosolgo Thank you - this is what I was looking for!

@rmosolgo rmosolgo merged commit 41b5b6c into 1.13.x Jan 10, 2023
@rmosolgo rmosolgo deleted the hash-lookup-1.13 branch January 10, 2023 19:37
@rmosolgo
Copy link
Owner Author

Great -- released to RubyGems in v1.13.18!

@alexcwatt
Copy link

I'm not seeing it here ... maybe due to this?

@rmosolgo
Copy link
Owner Author

🤦 🤦 🤦 Meanwhile, back in my terminal:

image

Amazingly, entering a live code hours later worked fine 😅 💁‍♂️ https://rubygems.org/gems/graphql/versions/1.13.18

Unfortunately that GitHub Action won't pass without a bit of work, since the workflow file is so old, so the docs won't get properly published...

@alexcwatt
Copy link

Thank you! I'll give it a try tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants