We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What is the reasoning behind only supporting labels on a subset of the components? Would it be possible to extend label support to all of them?
Additionally, could connections support labels as well?
The text was updated successfully, but these errors were encountered:
Components: Totally agree! Actually I'm working on it. In the next release each component will be able to handle labels.
Connections: they "should" already support labels (if something does not works please let me know, I'll fix it asap).
type Connection struct { Origin string `yaml:"origin"` Targets []struct { ID string `yaml:"id"` Label string `yaml:"label,omitempty"` Color string `yaml:"color,omitempty"` Dashed bool `yaml:"dashed,omitempty"` Dir string `yaml:"dir,omitempty"` Highlight bool `yaml:"highlight,omitempty"` } `yaml:"targets"` }
Sorry, something went wrong.
Fix: issue #5 and add new feat: load YAML from HTTP
5b49e2d
Fixed with release v0.7.0.
No branches or pull requests
What is the reasoning behind only supporting labels on a subset of the components? Would it be possible to extend label support to all of them?
Additionally, could connections support labels as well?
The text was updated successfully, but these errors were encountered: