You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to change back (was like this before) the API of the Condition to not only handle the resource:
boolean isMet(P primary, R secondary, Context<P> context);
but rather the dependent resource:
boolean isMet(P primary, D dependentResource, Context<P> context);
Rational: This will make a more generic api, where the distinction if its a bulk managed resource or other is done within the implementation. In case some implements a custom dependent resource and provides some additional functionalities that could be accessed also more elegantly.
The text was updated successfully, but these errors were encountered:
See this report for some details: #1687
The idea is to change back (was like this before) the API of the
Condition
to not only handle the resource:boolean isMet(P primary, R secondary, Context<P> context);
but rather the dependent resource:
boolean isMet(P primary, D dependentResource, Context<P> context);
Rational: This will make a more generic api, where the distinction if its a bulk managed resource or other is done within the implementation. In case some implements a custom dependent resource and provides some additional functionalities that could be accessed also more elegantly.
The text was updated successfully, but these errors were encountered: