-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Add interface IterableRelyingPartyRegistrationRepository or similar #15027
Comments
More context: I'm composing multiple repositories because I'm implementing metadata refresh, and it's considerably easier if a Although, as I've been typing this, I think it might be easier if I instead write a Edit: except you've made that difficult because Edit 2: also |
Expected Behavior
Current Behavior
Context
A mess develops when you start adding custom implementations that are also iterable, and/or writing e.g. custom login pages that need to iterate through all registrations. Especially if you're trying to compose multiple repositories because they need different behaviour,
You either have to resort to unchecked casts, or unpleasant generics like
<T extends RelyingPartyRegistrationRepository & Iterable<RelyingPartyRegistration>>
.I assume it's too late to make
RelyingPartyRegistrationRepository
extendIterable<RelyingPartyRegistration>
or to add a method that returns aCollection<RelyingPartyRegistration>
?The text was updated successfully, but these errors were encountered: