-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[query] Sample file not working #390
Comments
I'm too far away from my PC to test myself, but you might try enclosing |
Thank you @kvid. Here is the version number: wireviz 0.3.2 and it is Windows 64-bit operating system. |
Please check the indentation of your YAML file. When you copy it into GH, you can display it as a code block using triple ``` back quote characters.
|
Thank you! It works now. |
@akikinho - I'm glad your problem got solved, but please explain what you changed to solve the problem, so others with similar problems might learn from your use case. |
Hello @kvid, the indentation was not correct as per @martinrieder, so I corrected it in the YAML file. I find that Wireviz is indentation and format sensitive. |
Hello Wireviz Team,
I am faced with an issue which I am unable to diagnose and understand the reason. The error Exception: First item not found anywhere.
Thank you in advance!
connectors:
CX:
pincount: 49
type: Plug Housing
subtype: male
pins: [1,2,3,4,5,6,7,8,9,10,
11,12,13,14,15,16,17,18,19,20,
21,22,23,24,25,26,27,28,29,30,
31,32,33,34,35,36,37,38,39,40,
41,42,43,44,45,46,47,48,49]
S: &splice # generic autogenerated splice
style: simple
autogenerate: true
type: splice
show_name: true
SPLICE_CX:
<<: *splice # copy attributes from 'S'
autogenerate: false # but disable autogeneration
show_name: true # this is currently necessary when autogenerate == false
cables:
WIRE SPLICE_CX:
gauge: 1
type: TXL
wirecount: 3
show_equiv: true # auto-calculate AWG equivalent
colors: [RD,GN,SH]
shield: false # add cable shielding
category: bundle
wirelabels: [A,B,C]
connections:
The text was updated successfully, but these errors were encountered: