cannot change "stroke" of Axis
See original GitHub issueThe property “stroke” is not changable:
XAxis.defaultProps = {
stroke: "#000000", // x axis stroke coloe (TODO: should be named "color")
..
}
when using this:
<XAxis axisAt="bottom" orient="top" stroke="#ccc" tickStroke="#ccc"/>
<YAxis axisAt="bottom" orient="top" stroke="#ccc" tickStroke="#ccc"/>
only the color “tickStroke” is changed, but stroke does not change (it remains “#000000”).
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Adjust the stroke width's Y axis scale (only)
I just want to rescale the Y-axis of the stroke width so it doesn't become distorted when scaling back up. It is the...
Read more >Looking for a better way to alter the color of axis components ...
At this point the only method I have found to change the colour of the components is by individually setting styles in the...
Read more >How to change axes linewidth? - MATLAB Answers - MathWorks
go to edit -> axes properties and this will open up a property inspector. within this select "box styling" option and see the...
Read more >Apply and adjust stroke properties – Figma Help Center
Strokes are a collection of properties you can apply to layers in design files. You can think of strokes as the visual representation...
Read more >Customize X-axis and Y-axis properties - Power BI
You can add and modify the data labels and X-axis title. ... make the gridlines stand out by changing the color and increasing...
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 FreeTop 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
Top GitHub Comments
The behaviour of all these seperate items is so inconsistent, I believe a good refactoring to use helpers instead of bad copy/paste actions would be helping us a lot. I am wasting a lot of time figuring out why some items render both ‘555555’ and ‘#555555’, while others only render ‘555555’. What’s up with that? So weird, as if “smart logic” (decided by the programmer) (d)evolved over time and the landscape is filled with anomalies. BEWARE!!
Ugh, I don’t feel up to this…pfff
ah another property not consistently implemented between svg and canvas. Thanks for pointing it out. I will work on this soon