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
It seems that if, using the JS API (options object), you set valueText to anything that can be parsed as a number, it will be parsed as such and treated as falsy by the underlying canvas-gauges. This can result in some confusing glitches. I found that canvas-gauges on its own suffers from the same problem, but only if you use its HTML attribute API (data-value-text="0" appears falsy, which is really a limitation of the API's design). If you provide it an option object with valueText: "0", it is correctly treated as truthy and rendered.
ng-canvas-gauges should provide its values to canvas-gauges using the JS API to avoid this problem.
The text was updated successfully, but these errors were encountered:
It seems that if, using the JS API (
options
object), you setvalueText
to anything that can be parsed as a number, it will be parsed as such and treated as falsy by the underlyingcanvas-gauges
. This can result in some confusing glitches. I found thatcanvas-gauges
on its own suffers from the same problem, but only if you use its HTML attribute API (data-value-text="0"
appears falsy, which is really a limitation of the API's design). If you provide it an option object withvalueText: "0"
, it is correctly treated as truthy and rendered.ng-canvas-gauges
should provide its values tocanvas-gauges
using the JS API to avoid this problem.The text was updated successfully, but these errors were encountered: