kvid
kvid
Similar to the answers you got in #397 and #402, using a connector is currently the best we can offer to represent such components. You have now convinced me that...
@martinrieder wrote: > Maybe we need to make some destinguishment through another CLI argument that would request BOM output, templates and metadata to be included, which is currently only supported...
@formatc1702 - Is my original issue here trivial, or might there be bad side-effects? The suggestion by @martinrieder is also valid, but that must be handled later, in a separate...
Closed after releasing v0.4.1.
Please provide a YAML input example that demonstrates your issue. One commonly used function to make connectors more compact is to add `hide_disconnected_pins: true`.
I took the liberty to edit you message, by only adding YAML code tags around your YAML input to make it easier to read. Please verify that I didn't destroy...
WireViz v0.4 only supports a common `type` and `gauge` value for all wires in the same cable/bundle - see [syntax description](https://github.com/wireviz/WireViz/blob/v0.4/docs/syntax.md#cable-attributes), but #268 suggests supporting different gauges for each wire...
Please join the #268 discussion and present your use case and view to contribute to the on-going suggestions there.
This issue seems to be resolved. I copied your two latest comments into #268 as they seems to belong there.
This might be something I would really like! What is the easiest way to test this functionality before merging? Do I have to e.g. cherry-pick your commit into the `master`...