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.

Sign up for GitHub

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

Jump to bottom

Refactor: Rename ServiceBindingMerger to Outline it's actual Intention #43

Open
Johannes-Schneider opened this issue Aug 11, 2022 · 0 comments
Open

Refactor: Rename ServiceBindingMerger to Outline it's actual Intention #43

Johannes-Schneider opened this issue Aug 11, 2022 · 0 comments
Labels
breaking This issue needs breaking changes enhancement New feature or request

Comments

@Johannes-Schneider
Copy link
Contributor

Context

The class name of the ServiceBindingMerger is currently confusing as it doesn't actually merge individual ServiceBindings but instead it merges Collections of ServiceBindings.

Request

Find a better name for the ServiceBindingMeger that outlines it's actual intention.

Suggestions

Consider following names:

  • ServiceBindingCollectionMerger
  • ServiceBindingAggregator
@Johannes-Schneider Johannes-Schneider added enhancement New feature or request breaking This issue needs breaking changes labels Aug 11, 2022
@Johannes-Schneider Johannes-Schneider mentioned this issue Aug 11, 2022
Merged
@Johannes-Schneider Johannes-Schneider changed the title Fix: Rename ServiceBindingMerger to Outline it's actual Intention Refactor: Rename ServiceBindingMerger to Outline it's actual Intention Aug 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking This issue needs breaking changes enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Johannes-Schneider