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
If I have an dependentResource that extends from AbstractExternalDependentResource, but also from Updater, then the update will never be called when the Primary resource is updated. This is caused by a problem with the match method.
@BramMeerten I added a PR that might make this a bit more user friendly. There is no good solution for this IMO, the intention was that this is indeed overwritten. That is what the matcher method in the Updater should indicate. But this is complicated with the Bulk resources, where the matcher has different footprint and you want that to be defaulted that case. Pls check the PR if that makes sense, it provides a default not recursive implementation.
@csviri Looks good to me
Having to override matcher is no problem for me, the main problem that I had was that it wasn't working without any error that indicated what was wrong.
Somehow there was no stackoverflowexception because of infinite recursion, the recursion just stopped after a while.
If I have an dependentResource that extends from
AbstractExternalDependentResource
, but also fromUpdater
, then theupdate
will never be called when the Primary resource is updated. This is caused by a problem with thematch
method.For example this dependent resource:
This is caused by a method call to
match
that keeps calling itself:AbstractDependentResource::match
is called:match
method on the fieldupdater
, but this is the same dependent resource (ExternalUserDependentResource
in my example):Workaround:
Override
match
in the dependent resource and do the check yourself.The text was updated successfully, but these errors were encountered: