dashboard - consider dropping use of floppyforms?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Fix Released
|
Medium
|
zhurong |
Bug Description
Would it be possible to drop use of django-floppyforms from murano-dashboard? It doesn't seem to be very well supported anymore. Scrolling through the issues there are several unanswered for a long time [1] and there's not been a release in a long time [2]. This makes supporting the package in distros difficult in terms of support. The package was dropped from Ubuntu in Xenial (likely due to lack of use). In murano-dashboard, django-floppyforms was recently added to requirements.txt in commit caaa9ea88d163dc
[1] https:/
[2] https:/
summary: |
- dashboard - consider dropping use of floppyfroms? + dashboard - consider dropping use of floppyforms? |
Changed in murano: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
I'm not sure this code is even used.
muranodashboard /common/ widgets. py is the only module that imports from floppyforms, and floppyforms is used by class TriStateCheckbo xSelectMultiple .
The only place TriStateCheckbo xSelectMultiple is referenced is in muranodashboard /common/ fields. py, in the TriStateMultipl eChoiceField class.
However the TriStateMultipl eChoiceField class never appears to be used. Here's a recursive grep through the murano-dashboard code:
murano-dashboard$ grep -r TriStateMultipl eChoiceField /common/ fields. py:class TriStateMultipl eChoiceField( forms.ChoiceFie ld):
muranodashboard