forms and fields are not in a proper place

Bug #1287634 reported by Maxime Vidori
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Medium
Maxime Vidori

Bug Description

According to Django architecture, the fields need to be stored in the same place as the forms and be available through the same module. In horizon, fields are store in utils and need to be imported separately.

Changed in horizon:
assignee: nobody → Maxime Vidori (maxime-vidori)
status: New → In Progress
Julie Pichon (jpichon)
Changed in horizon:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/65983
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=cbb52ebc66de0524c8d63447dde7faf6cc2f591b
Submitter: Jenkins
Branch: master

commit cbb52ebc66de0524c8d63447dde7faf6cc2f591b
Author: Maxime Vidori <email address hidden>
Date: Fri Jan 10 16:22:10 2014 +0100

    Group specific fields in horizon.form module

        According to the Django architecture, all fields are grouped in
    the django.form module, Horizon fields were dispatched in two modules
    utils and form. This patch cleanup the loading of Horizon specific
    fields.

    Change-Id: Ib18848a8cc06dbd5984ec02d7cd647145124ced4
    Closes-Bug: #1287634

Changed in horizon:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in horizon:
milestone: none → juno-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in horizon:
milestone: juno-1 → 2014.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.