fixing an issue

[learner1024]

In Polymer, if a property is defined as Boolean, then presence of that property in markup will lead to be treated as value true even if value is false, e.g.
<px-vis-axis id="xaxis" prevent-series-bar="false"></px-vis-axis> will still consider it as true.

This happens for same reason, if("false") console.log("true") will be logging "true" on console.

More details can be found here.
Polymer/polymer#1812

one of solution, which I think is minimum impact silver bullet, is to have such properties defined as Object rather than Boolean.

I have made this change for preventSeriesBar for px-vis-axis, as we use that in px-vis-xy-chart and our use case only has one series so not having series bar on y axis would be nice.

I hope this helps

Sandeep Khandewale
(Consultant, GE Oil and Gas, Mumbai)

[nonmetalhail]

Correct. However, this is not a Polymer thing, this is HTML spec and I'm not sure we should stray from the HTML standard. It simply requires default states to be considered in designing the API.

Polymer does make it easy to set booleans to false. Declaratively bound properties will trigger a false boolean and imperatively setting booleans to false works fine.

Although using objects to force computation of the boolean state is clever, I'm concerned with clarity in the documentation. With Boolean properties, it is clear what valid entries are. If the type is object, that is no longer the case.

We'll talk about it and see.

[mdwragg]

I agree with @nonmetalhail, not sure about this approach...

[nonmetalhail]

Thinking about this more, I bet that changing the type to Object also break standard Boolean behavior wherein you do not need to provide a value. We definitely dont want to stray from HTML spec in this way.