Inconsisten left padding (with data vs without data)

[LeonardAB]

Description

When creating a graph bar, I found that the left padding (distance between the Y axis with the graph's container border) to be inconsistent between when there is data and no data.
When there is no data, the padding becomes a lot smaller.

Steps to check or reproduce

https://jsfiddle.net/pg1yq2fh/3/

with data:

without data (in the JS, comment/uncomment the relevant dataset). This happens even when tick values are added manually.

[netil]

Hi @LeonardAB, this is the result of y Axis options - padding, tick.values and tick.count collision.

• tick.count: the y Axis value will be determined in a range of the current y domain value.
• tick.values: the y Axis tick values will be determined as the given values based on the current y Axis domain value.

So, setting both tick.count and tick.values options together will likely have some inconsistency to determine "final" tick values.

y: {
    tick: {
        values: yTicks, // without 'tick.count' option, will display as the right screenshot
        count : 5 // without 'tick.values' option, will display as the left screenshot
    }
}

Having both options set will use tick.values for final tick text value, but why left padding is there?
The main reason as to be rendered having spaced left padding is because in the process of determining y Axis tick value.

Even isn't displayed, the tick.count option makes to calculate tick text space as the left screenshot.
To avoid this, make sure to use one of the options, not both.

I'll be fixing this issue to not count if tick.values option is set.

[netil]

🎉 This issue has been resolved in version 1.12.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀