Feature/refactor operation naming #5
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
The change prevents the need to alias when working with different resource operations. BREAKING CHANGE: All operation classes have been renamed, this will require consumer class instantiations to be updated accordingly.
mikeymike
force-pushed
the
feature/refactor-operation-naming
branch
from
6781e17 to
13f2505
Compare
vifer
approved these changes
Jan 23, 2024
|
README.md needs updating |
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.
The change prevents the need to alias when working with different resource operations.
After some discussion it felt like this change is very beneficial and while we're
<1.0.0it's the best time to get this in.Note this is a breaking change All operation classes have been renamed, this will require consumer class instantiations to be updated accordingly.