Column.empty_value should accept a callable

Bug #999370 reported by Gabriel Hurley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Wishlist
Gabriel Hurley

Bug Description

It would be both more consistent and more useful if tables.Column.empty_value could accept a callable that was able to determine the empty value based on attributes of the object. For example, being able to differentiate a field that's empty because it's not permitted/not applicable versus a field that's empty simply because the value isn't set.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/7416

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/7416
Committed: http://github.com/openstack/horizon/commit/7fed6d662065f9917e3fd62d14dd69733cc178d9
Submitter: Jenkins
Branch: master

commit 7fed6d662065f9917e3fd62d14dd69733cc178d9
Author: Gabriel Hurley <email address hidden>
Date: Mon May 14 15:15:49 2012 -0700

    Make empty_value accept a callable.

    Fixes bug 999370.

    Change-Id: I0c3f830396645b261e4eb71c7b3d59560c913c6f

Changed in horizon:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in horizon:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: folsom-1 → 2012.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.