Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Plot and style option name clashes
See original GitHub issueThe new .options method relies on unique names for plot and style options. At least in one case that is currently not true, namely the width option on Bars is both a plot options (controlling the width of the plot) and a style option (setting the width of the bars). We need to validate that these do not clash, and in the case of width rename the width style option to bar_width.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Error: option 'name' clashes with existing property ...
The issue is that I am now having some trouble with some of the newer modules I just installed with npm. This error...
Read more >LaTeX Error: Option clash for package xcolor
The beamer class loads xcolor per default. You can issue the option via a beamer -option \documentclass[10pt,xcolor={usenames}]{beamer}.
Read more >Error in the check for option name clash function in 6.0.0
It seems to me that there is a bug in the new name clash feature. I do have a clash where there should...
Read more >Command: clashes, contacts
When multiple pseudobond models have the same name, specific models can be removed with the close command. Normally, a clash or contact is...
Read more >Five Elements of Fiction: Plot, Setting, Character, Point of ...
2) Rising Action - Events in the story become complicated; the conflict is revealed. These are events between the introduction and climax. •...
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
Okay, I’ve come up with a plan for this, I’m going to make sure that plot options take precedence over style options in the
expand_optionsmethod, since those are more common. For now we will leave the clashing style options registered, which means that they can still be set usingoptsor the magic but I will also register the new non-clashing names as aliases. Eventually we can deprecate the clashing options.Sounds good.