-
Notifications
You must be signed in to change notification settings - Fork 62
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
Update behavior of ObjectContainer.IsRegistered()
to check base container for registrations
#367
Merged
gasparnagy
merged 6 commits into
reqnroll:main
from
DrEsteban:DrEsteban-IsRegisteredAtAnyLevel
Feb 3, 2025
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
ec48b65
Adding IsRegisteredAtAnyLevel() to ObjectContainer
7f54aae
Update CHANGELOG
e937dc6
Update registration method summaries in IObjectContainer
DrEsteban 7713d5b
PR feedback: Change behavior of IsRegistered()
52f2e63
Merge branch 'main' into DrEsteban-IsRegisteredAtAnyLevel
f2b2d0e
Update changelog
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given this is a "breaking"/behavior change, is there any major/minor version specification I should be revving as part of this PR? Or will maintainers handle that as part of the next release?
Is this message clear enough to indicate it's a behavior change? I see historical change entries for bug fixes have a
Fix:
prefix, and new features/support seem to not have anything. Should there be aBreaking:
(or similar) prefix to this one? (It could be argued it's aFix
for behavior it should have always had...or a "design bug fix"...but it's not really a traditional code bug.)If you'd like any of the above☝️ concepts solidified, let me know and I can create another PR to update the
CONTRIBUTING.md
.