You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check this if you would like to implement a PR, we are more than happy to help you go through the process.
What problem are you trying to solve?
Currently, the Line component in the react-chartjs-2 package requires a minimum of three data points to render a smooth curve using the tension property. This limitation poses a problem for cases where you only have two data points but still wish to display a curved line between them. Without the ability to use the tension property with just two data points, the line appears as a straight line, which can be less visually informative or aesthetically pleasing.
Actual Screenshot:
Expected Screenshot:
Describe the solution you'd like
I would like to request an enhancement to the Line component in the react-chartjs-2 package to allow the use of the tension property with a minimum of two data points.
Describe alternatives you've considered
No response
Documentation, Adoption, Migration Strategy
No response
The text was updated successfully, but these errors were encountered:
Would you like to work on this feature?
What problem are you trying to solve?
Currently, the Line component in the
react-chartjs-2
package requires a minimum of three data points to render a smooth curve using the tension property. This limitation poses a problem for cases where you only have two data points but still wish to display a curved line between them. Without the ability to use the tension property with just two data points, the line appears as a straight line, which can be less visually informative or aesthetically pleasing.Actual Screenshot:
Expected Screenshot:
Describe the solution you'd like
I would like to request an enhancement to the Line component in the react-chartjs-2 package to allow the use of the tension property with a minimum of two data points.
Describe alternatives you've considered
No response
Documentation, Adoption, Migration Strategy
No response
The text was updated successfully, but these errors were encountered: