Add dig and fetch to Sawyer::Resource
#74
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These convenience methods make it easier to work with `Resource`s as a consumer, especially when they come from APIs that have a lot of nesting. Supporting these methods, in addition to `[]`, `[]=`, `each`, and all the other enumerable methods, allows consumers to treat a `Sawyer::Resource` effectively as a Hash for the attributes without having to convert it to one and lose the extra behavior that the `Resource` provides.
iMacTia
approved these changes
Jun 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These convenience methods make it easier to work with
Resources as a consumer, especially when they come from APIs that have a lot of nesting. My particular motivation comes from using Octokit, which returnsSawyer::Resources, and I routinely try todigorfetchfrom them, at which point my code blows up, and I don't want to convert the whole thing to a hash to get just the one bit of data I need.Supporting these methods, in addition to
[],[]=,each, and all the other enumerable methods, allows consumers to treat aSawyer::Resourceeffectively as a Hash for the attributes without having to convert it to one and lose the extra behavior that theResourceprovides.