New username: @17o2

> I guess @formatc1702 is thinking about internally in his WireViz Python code, not internally in the users organization, and also input and output files related to this WireViz tool....

FYI, everyone interested: Support for custom units has been added to the `dev` branch in #196; auto-parsing (`length: 5 in` yielding `length: 5` and `length_unit: in`, analogous to how wire...

Some thoughts on this: - Strictly speaking, this should be a property of the cable (`label` or similar), and it should allow for different labels on either end, something like...

Alternative implementation idea (separate and independent from the `additional_attributes` proposal): - You need the label to appear in the BOM - If multiple cables use the same type of label...

Hi, sorry for ignoring this issue and the associated PR for this long. This is an interesting idea... can you explain a real-life situation where this might come in handy?...

Thanks for the input. I am currently refactoring the entire graph generation code, so I will keep this edge case in mind. Is there a way to see some of...

I hadn't thought of any EDA tool integration (could you describe a specific usecase for this?) but a sort of netlist output has been on my mind. Simply a table...

My initial reaction is to specify the ferrules as additional BOM items (as per #115) like @kvid suggests. otherwise, you would need to define a connection between two connectors directly,...

I was thinking of having a separate section in the YAML file. `connections` could remain unchanged, for strict connector-cable-connector-[...] sequences. A new section, `mates` or similar, could define mechanical matings...

Renamed issue title to consolidate with #148.