numerical arguments with defaults of 0 are passed as None

Bug #1291084 reported by Doug Hellmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
WSME
Fix Released
High
Doug Hellmann

Bug Description

With a controller that takes integer arguments defaulting to 0, if the value is not passed in the request the controller receives None instead of 0.

For an example of a controller like that see http://paste.openstack.org/show/73192/

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

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

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

Reviewed: https://review.openstack.org/79793
Committed: https://git.openstack.org/cgit/stackforge/wsme/commit/?id=9c8a033415606667eca915c863165e5f9021bccb
Submitter: Jenkins
Branch: master

commit 9c8a033415606667eca915c863165e5f9021bccb
Author: Doug Hellmann <email address hidden>
Date: Tue Mar 11 15:44:06 2014 -0700

    Fix default handling for zero values

    When int and float arguments to controllers default to zero and no value
    is provided in the request, the controller is being passed None instead
    of 0.

    Closes-bug: #1291084
    Change-Id: I35c034e4a793a44d2ddd376046e7dbb841ca13b6

Changed in wsme:
status: In Progress → Fix Committed
Changed in wsme:
milestone: none → 0.8.0
status: Fix Committed → Fix Released
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.