l3_proactive_app naming convention is unclear
Bug #1653926 reported by
Omer Anson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DragonFlow |
Fix Released
|
High
|
Omer Anson | ||
Bug Description
The names of methods in the L3 proactive application are unclear. They do not explain what the method does, but more like in what context it should be used.
This bug exists so that this will be corrected. There are two action items:
* Rename each method to state its function
* Add pydoc for each method.
| Changed in dragonflow: | |
| assignee: | nobody → Omer Anson (omer-anson) |
| Changed in dragonflow: | |
| importance: | Medium → High |
| Changed in dragonflow: | |
| assignee: | Omer Anson (omer-anson) → nobody |
| Changed in dragonflow: | |
| assignee: | nobody → Omer Anson (omer-anson) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to dragonflow (master) | #1 |
| Changed in dragonflow: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to dragonflow (master) | #2 |
| Changed in dragonflow: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/