0, false, empty === undefined

Site and Services
#1

if I set item id to 0 or false, webix does not see it and sets its own id.
as I see, webix checks it like !(item.id) and as a result I cannot use items with those ids. it matters especially in combo (select, richselect) views. why not to use webix.isUndefined in such cases?
http://webix.com/snippet/b5090400

#2

For now, it’s a necessary limitation for the data components (item’s id shouldn’t be0,false ornull). We do not plan to change this behavior.

#3

the issue is solved. actually, the problem was that I used an array of {id, value} objects in select options. in this case a widget changes id if it is empty. but when a plain object is used for options (e.g. {0:“Default”, 1:“Any value”}) everything goes normal.