We have a lot of places with the init-calls-subclass pattern.
This cause problems if the subclass method relies on subclass attributes that have not yet been set up.
I actually ran into the issue in #12215.
- Has anyone encountered this before?
- Do we have a strategy how to avoid this issue?
We have a lot of places with the init-calls-subclass pattern.
This cause problems if the subclass method relies on subclass attributes that have not yet been set up.
I actually ran into the issue in #12215.