Charlie Brown

We removed all defaultProps a couple versions ago, but it could be coming from a dependency. Which version are you using our `react-live`?

Additional example with much simpler setup: https://codesandbox.io/s/single-point-flickering-076ox?file=/src/Components/VictoryLineDemo.tsx

We are focusing our efforts on a rebuild of Victory specific to native in https://commerce.nearform.com/open-source/victory-native/

@lealcy Could you provide some more information and a code example to reproduce? Which browser, font settings, and css are you using? Are you able to replicate the issue in...

That's the same I'm running as well, but I'm not able to reproduce it.  If you have custom CSS, sometimes line heights can interfere. Could you share some example...

The docs have some examples on using multiple axes in Victory https://commerce.nearform.com/open-source/victory/gallery/multiple-dependent-axes

By default, all axes under a `VictoryChart` will be rendered in the same domain, but you can create a custom chart with independent axes by following this example here https://commerce.nearform.com/open-source/victory/guides/custom-charts

With the increasing usage of Graphql, we are seeing this more often as well. The entry name is the same for dozens of requests on every page load. Since they...

Adding a random character to mark something private is unneccessary syntax. The compiler can treat it as such as well as any decent IDE. I suggest marking it as `private`...

I would like to say that should be a compiler error, since using call in that way violates everything OOP about classes...but your right, its still supported.