Skip to content

Commit fab3479

Browse files
committed
Fix numbered lists
1 parent 457ece1 commit fab3479

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/codeql/codeql-cli/extractor-options.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,8 +88,8 @@ Setting extractor options from files
8888

8989
You can also set extractor options through a file. The CodeQL CLI subcommands that accept ``--extractor-option`` also accept ``--extractor-options-file``, which has a required argument of the path to a YAML file (with extension ``.yaml`` or ``.yml``) or a JSON file (with extension ``.json``). For example:
9090

91-
# ``codeql database create --extractor-options-file options.yml ...``
92-
# ``codeql database start-tracing --extractor-options-file options.json ...``
91+
* ``codeql database create --extractor-options-file options.yml ...``
92+
* ``codeql database start-tracing --extractor-options-file options.json ...``
9393

9494
Each option file contains a tree structure of nested maps. At the root is an extractor map key, and beneath it are map keys that correspond to extractor names. Starting at the third level, there are extractor options and option groups.
9595

@@ -134,7 +134,7 @@ Assigning an extractor option that does not exist is an error. You can make the
134134

135135
You can specify ``--extractor-options-file`` multiple times. The extractor option assignments are processed in the following order:
136136

137-
# All extractor option files specified by ``--extractor-options-file`` are processed in the order they appear on the command line, then
138-
# All extractor option assignments specified by ``--extractor-option`` are processed in the order they appear on the command line
137+
1. All extractor option files specified by ``--extractor-options-file`` are processed in the order they appear on the command line, then
138+
2. All extractor option assignments specified by ``--extractor-option`` are processed in the order they appear on the command line
139139

140140
The same rules govern what happens when the same extractor option is set multiple times, regardless of whether the assignments are done using ``--extractor-option``, using ``--extractor-options-file``, or some combination of the two. If you set a ``string`` extractor option multiple times, the last option value overwrites all previous values. If you set an ``array`` extractor option multiple times, all option values are concatenated in order.

0 commit comments

Comments
 (0)