New username: @17o2

> There are also several other exceptions in WireViz that need improvements like this. Maybe we should raise a more general issue to identify more of them? **Yes.** More user-friendly,...

There has been some progress in #189 regarding this issue, @gmkado please have a look and feel free to post feedback.

This PR is ready for review. I have been using this feature and the included DIN 6771 template files for quite a while and I am very pleased with the...

> * This preliminary review is only based on inspection of changes, not testing. Thanks, I will incorporate some of your changes soon and wait for some testing. > *...

Hi, could you provide a specific example of how you would use this for WireViz? I am not sure I understand what it is you want to turn into a...

> AFAIK, this is by design. Correct. Here's the history: - At the beginning, the only parameter that could change on a per-wire basis, was color. Everything else (type, length,...

This sounds extremely useful, but will require some rewriting of the input checking logic, since so far it has been a strict CABLE-CONNECTOR-CABLE-CONNECTOR-.... sequence. It's a good task to tackle...

Naïve question: Is there a way to unify connectors and these components somehow in the YAML? I understand that currently, the BOM entry auto-appends the "Connector" prefix, which is unwanted...

This may be only partially related, but this is how I implemented including a little level shifter PCB in one of our wiring diagrams at work (using the `feature/mate+autogenerate` branch...

If you're only using the code on the `master` branch, you'll be pleased to know that better looking cables are on their way. Have a look at the [example gallery...