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
Much like the OverrideField, calls to the parentConfiguration cause unnecessary overhead, due to the depth of the call tree. As the result of those calls are not cached in a field, in contrast to the OverrideField where every value was cached, the overhead is potentially higher.
The solution would be to introduce fields in the OverrideConfiguration for every field that is retrieved from the parentConfiguration, and fill those fields on initialisation of the OverrideConfiguration.
The text was updated successfully, but these errors were encountered:
Much like the OverrideField, calls to the parentConfiguration cause unnecessary overhead, due to the depth of the call tree. As the result of those calls are not cached in a field, in contrast to the OverrideField where every value was cached, the overhead is potentially higher.
The solution would be to introduce fields in the OverrideConfiguration for every field that is retrieved from the parentConfiguration, and fill those fields on initialisation of the OverrideConfiguration.
The text was updated successfully, but these errors were encountered: