Ensure to use api.<category>.<method>
In the current code both api.<method> and api.<category>.<method> are used. Using api.<method> directly makes it difficult to identify which module defined a method and forces developers to use unique method names among projects. This commit removes api.<method> style method calls. Change-Id: Iaefa1061f99b7865e02541df87c112a6b2868ec0
This commit is contained in:
parent
32fa91d9f1
commit
86fead3196
|
@ -32,9 +32,10 @@ In other words, Horizon developers not working on openstack_dashboard.api
|
||||||
shouldn't need to understand the finer details of APIs for
|
shouldn't need to understand the finer details of APIs for
|
||||||
Keystone/Nova/Glance/Swift et. al.
|
Keystone/Nova/Glance/Swift et. al.
|
||||||
"""
|
"""
|
||||||
from openstack_dashboard.api.glance import *
|
from openstack_dashboard.api import base
|
||||||
from openstack_dashboard.api.keystone import *
|
from openstack_dashboard.api import cinder
|
||||||
from openstack_dashboard.api.nova import *
|
from openstack_dashboard.api import glance
|
||||||
from openstack_dashboard.api.swift import *
|
from openstack_dashboard.api import keystone
|
||||||
from openstack_dashboard.api.quantum import *
|
from openstack_dashboard.api import nova
|
||||||
from openstack_dashboard.api.cinder import *
|
from openstack_dashboard.api import quantum
|
||||||
|
from openstack_dashboard.api import swift
|
||||||
|
|
Loading…
Reference in New Issue