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
Curently in a bundle the part number fields will be rendered differently if they are a string or a list. If they are a string they are rendered at the top of a node and if a list they are rendered per wire, it mould make sense for this to be consistent across bundles by always doing the latter.
The text was updated successfully, but these errors were encountered:
AFAIK, this is by design. Attributes common to all wires are listed above all wires (except image, and notes below all wires), and attributes specified for each wire are listed above and below each wire. Currently, both options are implemented for pn, manufacturer, and mpn, but it has been discussed to support the same for gauge too.
At the beginning, the only parameter that could change on a per-wire basis, was color. Everything else (type, length, gauge, ...) was global for the entire cable, thus displayed above the wires.
Currently, bundles implement separate [manufacturer] part number parameters.
That's why, IMHO, we shouldn't see this as a bug, nor worry about it too much, because I think some major refactoring may be in order to cleanly implement the transition for more granularity.
Splitting out of #115 (comment)
Curently in a bundle the part number fields will be rendered differently if they are a string or a list. If they are a string they are rendered at the top of a node and if a list they are rendered per wire, it mould make sense for this to be consistent across bundles by always doing the latter.
The text was updated successfully, but these errors were encountered: