Remove YAxis Custom Min/Max Check for Padding

[almic]

I noticed that while trying to add spacing to the bottom of a chart, to allow for the interior labels enough room that they don't overlap the data, nothing was happening. I was confused as to why setting the bottom spacing was doing literally nothing, and discovered it was disabled if the min was manually changed.

I thought it strange to disable this without mentioning anywhere in the documentation that this behavior was intentional. Adding percentage based padding let's developers easily add this extra space, but disabling it doesn't make sense. If developers don't want that extra spacing, they'll do what they would've done anyway, set the spacing to 0, as the default is 10%.

Since this behavior of disabling the spacing if custom values are set, even though the calculated range is BASED on those custom values, is not mentioned in documentation, I doubt this will cause any current compatibility issues, especially since the change will likely not be visually noticeable in the first place.

I really hope you can push this into the main library, as I think it makes more logical sense this way. Currently, I'm just re-calculating the min value myself, and then setting the new min with padding.

[almic]

Well since no one has commented on this I guess it's cool to add but whatever 😞

[danielgindi]

This should be reverted. What it does is strip customAxisMin/Max of its meaning.
Because you are recalculating it based on the auto-calculated min/max + spacing, where custom means a completely different value set manually.

You could take this into account in a different way, but your implementation actually hurts a fundamental feature badly.

[danielgindi]

I see that it was reverted in a later PR.