Fixing .rst file issues
Correcting errors in rst file formatting. Partial-Bug: #1486222 Change-Id: Id0a703d42609165a17ca84dade94b2c04894e208
This commit is contained in:
parent
776f945367
commit
6fbb70ebf2
@ -284,6 +284,7 @@ Required
|
||||
|
||||
2. Avoid in-lining styles into element in HTML. Use attributes and
|
||||
classes instead.
|
||||
|
||||
* In our JS files, we should focus on logic rather than attempting to
|
||||
manipulate/style elements.
|
||||
|
||||
@ -296,6 +297,7 @@ Required
|
||||
|
||||
3. Avoid using classes for detection purposes only, instead, defer to
|
||||
attributes. For example to find a div:
|
||||
|
||||
.. code ::
|
||||
|
||||
<div class="something"></div>
|
||||
|
@ -187,7 +187,7 @@ You can generate various reports and metrics using command line arguments
|
||||
to ``run_tests.sh``.
|
||||
|
||||
ESLint
|
||||
----
|
||||
------
|
||||
|
||||
To run ESLint, a JavaScript code style checker::
|
||||
|
||||
|
@ -146,7 +146,9 @@ Upstream
|
||||
JavaScript files can be discovered automatically, handled manually, or a mix of
|
||||
the two. Where possible, use the automated mechanism.
|
||||
To use the automatic functionality, add::
|
||||
AUTO_DISCOVER_STATIC_FILES = True
|
||||
|
||||
AUTO_DISCOVER_STATIC_FILES = True
|
||||
|
||||
to your enabled file (``enabled/<plugin_name>.py``). To make this possible,
|
||||
you need to follow some structural conventions:
|
||||
|
||||
|
@ -65,7 +65,9 @@ Jasmine uses suites and specs:
|
||||
|
||||
``.spec.js`` files can be handled manually or automatically. To use the
|
||||
automatic file discovery add::
|
||||
AUTO_DISCOVER_STATIC_FILES = True
|
||||
|
||||
AUTO_DISCOVER_STATIC_FILES = True
|
||||
|
||||
to your enabled file. JS code for testing should use the extensions
|
||||
``.mock.js`` and ``.spec.js``.
|
||||
|
||||
|
@ -512,12 +512,13 @@ OpenStack dashboard to use a specific API version for a given service API.
|
||||
The version should be formatted as it appears in the URL for the
|
||||
service API. For example, the identity service APIs have inconsistent
|
||||
use of the decimal point, so valid options would be "2.0" or "3".
|
||||
For example,
|
||||
OPENSTACK_API_VERSIONS = {
|
||||
"data-processing": 1.1,
|
||||
"identity": 3,
|
||||
"volume": 2
|
||||
}
|
||||
For example::
|
||||
|
||||
OPENSTACK_API_VERSIONS = {
|
||||
"data-processing": 1.1,
|
||||
"identity": 3,
|
||||
"volume": 2
|
||||
}
|
||||
|
||||
``OPENSTACK_ENABLE_PASSWORD_RETRIEVE``
|
||||
--------------------------------------
|
||||
|
@ -49,7 +49,7 @@ __all__ = [
|
||||
"IPv4",
|
||||
"IPv6",
|
||||
"MultiIPField",
|
||||
"SelectWidget"
|
||||
"SelectWidget",
|
||||
|
||||
# From django.forms
|
||||
"ValidationError",
|
||||
|
Loading…
Reference in New Issue
Block a user