Crosshair does not work when xType="time"
See original GitHub issueThe xType=“time” is working great on a LineSeries, but when I attempt to display a Crosshair that appears over the corresponding x-axis value, I get errors due to Date being an object.
The data used by the crosshair values
prop is the same as what the LineSeries is receiving.
The error message:
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Why Pros Use A Custom Crosshair in Fortnite! (Not Bannable?)
Why Pros Use A Custom Crosshair in Fortnite! ( Not Bannable?)In today's video I explain why you've recently seen pros use custom crosshairs...
Read more >How To Get A Custom Crosshair In Fortnite - YouTube
0:00 Intro0:16 Using a third-party crosshair overlay1:04 Using your gaming monitor's custom crosshairLearn how to get a custom crosshair in ...
Read more >The BEST Crosshair & Settings For VALORANT - YouTube
Have no idea what the best crosshair and settings are when playing Valorant? This video is for you. Valorant actually gives the user...
Read more >The BEST PRO Crosshair Settings for Valorant - YouTube
The BEST PRO CROSSHAIR SETTINGS for Valorant that will get you MORE KILLS!▻GET THE RANK YOU'VE ALWAYS WANTED: ...
Read more >VALORANT on Twitter: "You may have seen your crosshair ...
Not just my settings, but everything reset. Season progression, unlocked characters, items, everything - all gone. It's like I've never launched the game....
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
@ejmudrak I was having the same issue and the way to get around it is by adding a titleFormat to the Crosshair which would convert from a date object to a string which which is a valid react child. This way you don’t disrupt the auto positioning of the crosshair.
Thanks a ton @truncs
I had to convert it back to a date, but the Crosshair now positions correctly for dates! I also had to make sure that my function for
onNearestX
didn’t touch any formatting.