Mmmm interesting.
Why not send the $self object to plugin
and call SUPER::store() after hook ?
Best regards,
Le 10/03/2021 à 09:22, Jonathan Druart a écrit :
From perlobj pod:
"The |SUPER| pseudo-class is resolved from the package where the call is
made. It is /not/ resolved based on the ob
What was it?
El vie, 12 mar 2021 a las 10:17, muiru james ()
escribió:
> The backups issue was resolved.
>
> Thanks you
>
> On Wed, Mar 10, 2021 at 11:18 AM muiru james wrote:
>
> > Hello team,
> >
> > I have a system that has no backups to download at the export data,
> > backups in the tools m
So to have a "post_creation" hook that would be actually called *before*
the item is effectively created, hum... :)
Le ven. 12 mars 2021 à 13:47, Fridolin SOMERS
a écrit :
> Mmmm interesting.
>
> Why not send the $self object to plugin
> and call SUPER::store() after hook ?
>
> Best regards,
>
Oh indeed,
So maybe :
1) call SUPER::store()
2) call hook with $self
3) call SUPER::store() incase $seft has changed
What do you think ?
2) must call $seft->discard_changes right ?
Le 12/03/2021 à 15:14, Jonathan Druart a écrit :
So to have a "post_creation" hook that would be actually called
What are you actually trying to accomplish? Do you really need the
post-store object?
El vie., 12 mar. 2021 12:34, Fridolin SOMERS
escribió:
> Oh indeed,
>
> So maybe :
> 1) call SUPER::store()
> 2) call hook with $self
> 3) call SUPER::store() incase $seft has changed
>
> What do you think ?
>
