Adapt to semantic versioning

[scris]

Thank you for your brilliant work! This can be the best flutter package to build charts. However, recently I met an issue.

When upgrading from 2.6.9 to 2.8.0, I was informed that:

• (For DChartBarT) The named parameter 'outsideBarLabelStyle' isn't defined
• (For DChartBarT) The named parameter 'barLabelDecorator' isn't defined
• (For MeasureAxis) The named parameter 'labelFormat' isn't defined
• (For DomainAxis) The named parameter 'labelFormatterT' isn't defined

I was happy to see that this package is actively maintained, but may I request that this package can adapt to semantic versioning? That means, when some changes that will break prior user code usages take place, the version will bump from 2.x.x to 3.0.0, clearly informing the package users that there are some break changes need to be taken care of after upgrading.

Thanks for your precious time. Best wishes.

[indratrisnar]

Thanks for your advice For all that property, there is some changes. You can check on changelog. For label style move to BarLabelDecorator, for BarLabelDecorator move to ConfigRenderBar, for labelFrmat in domainAxis change to tickLabelFormatterT Pada Sel, 16 Jul 2024 23.10, Tianze Ds ***@***.***> menulis:

…

Thank you for your brilliant work! This can be the best flutter package to build charts. However, recently I met an issue. When upgrading from 2.6.9 to 2.8.0, I was informed that: - (For DChartBarT) The named parameter 'outsideBarLabelStyle' isn't defined - (For DChartBarT) The named parameter 'barLabelDecorator' isn't defined - (For MeasureAxis) The named parameter 'labelFormat' isn't defined - (For DomainAxis) The named parameter 'labelFormatterT' isn't defined I was happy to see that this package is actively maintained, but may I request that this package can adapt to semantic versioning? That means, when some changes that will break prior user code usages take place, the version will bump from 2.x.x to 3.0.0, clearly informing the package users that there are some break changes need to be taken care of after upgrading. Thanks for your precious time. Best wishes. — Reply to this email directly, view it on GitHub <#31>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APTLYD3KY45VEWEOG6B22PTZMVAYZAVCNFSM6AAAAABK65HVYSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGQYTCNJVHEZDGNA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[indratrisnar]

you can check this for example to use new property

[pvaibhav]

Same, also happy to see the package well maintained, but would appreciate if semantic versioning is followed. The breaking API changes are not too big but it still deviates from semver conventions. Thanks.