[BUG] GraphvizVertexShape.Record causes Label string to be empty on output.
See original GitHub issueWhen using ToGraphviz and the FormatVertex handler, when you assign the args.VertexFormat.Shape the value GraphvizVertexShape.Record, when the dot is output, the Label ends up empty despite assigning any string value to the Label, let alone that you would expect to be able to use the record formatting on. i.e. “{ a | b | c }”.
e.g. Expected gv output:
...
0 [shape=record, label="{ a | b | c }"];
Actual gv output:
...
0 [shape=record, label=""];
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
XmlPeek empty string causes failure - msbuild
The error happens because an empty string is being used as the Item Identifier. I guess identifiers cannot be the empty string.
Read more >[BUG] A mutation that adds a label removes empty strings ...
A mutation that adds a label removes empty strings from a Secret on updates. This is a problem, because applications might expect a...
Read more >Use empty string, null or remove empty property in API ...
Going with an empty string is a definitive no. Empty string still is a value, it is just empty. No value should be...
Read more >Empty string token causing multiselect box visual bug
I am using multiselect boxes to select which search results i want to exclude and include, and when the boxes are cleared, ...
Read more >The quikgraph from KeRNeLith - Coder Social
[BUG] GraphvizVertexShape.Record causes Label string to be empty on output. When using ToGraphviz and the FormatVertex handler, when you assign the args.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

That’s not publish to NuGet.org but to MyGet for now (snapshot). Note that it seems to be an issue on Microsoft side for symbol packages, because it’s not the real package that trigger those errors. On my side if I’m not wrong I set authors as requested, the problem is the procedure to geneate symbol package that voluntarily skips/removes this information. Didn’t remember the reason that was given by Microsoft team. Anyway this should not be an issue but it would be nice if they update nuget.exe to not raise those errors while being in their standard process. I may have to re-check if there were changes for this by the way.
I think we can indeed go this way for the
Label/Recordmanagement as it still allows to use Record structure but also extends to custom generated record, while enforcing the logic to not set both at the same time to avoid conflicts.