List Properties return None by default
Bug #1255903 reported by
Steven Hardy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
List properties, and probably also map, return None by default, which is inconvenient if you want to iterate over a property as you have to remember to default to an empty list either in the schema or when getting the property.
This is inconvenient and error prone, and can easily result in a 'NoneType' object is not iterable error when people forget.
It may be better, long term, to default these in the top-level Property class, Zane has suggested we need to do an audit of all existing uses of these type of properties to ensure nothing breaks.
Changed in heat: | |
assignee: | nobody → pradeep kumar singh (pradeep-singh-u) |
Changed in heat: | |
assignee: | Pradeep Kumar Singh (pradeep-singh-u) → nobody |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
To post a comment you must log in.
Everything returns None by default.