forms and fields are not in a proper place
Bug #1287634 reported by
Maxime Vidori
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 |
Changed in horizon: | |
importance: | Undecided → Medium |
Changed in horizon: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/65983 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=cbb52ebc66d e0524c8d63447dd e7faf6cc2f591b
Committed: https:/
Submitter: Jenkins
Branch: master
commit cbb52ebc66de052 4c8d63447dde7fa f6cc2f591b
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: Ib18848a8cc06db d5984ec02d7cd64 7145124ced4
Closes-Bug: #1287634