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 DefaultFactoredCustomer type is designed to encapsulate a list of CapacityBundle instances, and it's the CapacityBundles that evaluate tariffs and hold TariffSubscriptions. At this point there do not appear to be any FactoredCustomer instances that take advantage of this design, but it's the CapacityBundle that holds the CustomerInfo. It is not at all clear how this feature could be used correctly. Unless someone comes up with a compelling reason to retain this feature, I recommend we remove it and either fold CapacityBundle into FactoredCustomer or make the relationship 1:1.
The text was updated successfully, but these errors were encountered:
The DefaultFactoredCustomer type is designed to encapsulate a list of CapacityBundle instances, and it's the CapacityBundles that evaluate tariffs and hold TariffSubscriptions. At this point there do not appear to be any FactoredCustomer instances that take advantage of this design, but it's the CapacityBundle that holds the CustomerInfo. It is not at all clear how this feature could be used correctly. Unless someone comes up with a compelling reason to retain this feature, I recommend we remove it and either fold CapacityBundle into FactoredCustomer or make the relationship 1:1.
The text was updated successfully, but these errors were encountered: