Use consistent naming across resource methods #327
Merged
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.
Description
This PR introduces a refactor for several methods that poorly express an action on a relationship between two resources. By using verbs, we can be more specific as to what action we're performing when calling these methods. An example would be
ModuleConsumers()
-- from this method signature we can't necessarily tell what action this method is performing withoutreferring to the docs. Renaming it to
ListModuleConsumers()
we can now assess what the function does more conveniently.