You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/codeql/codeql-cli/about-ql-packs.rst
+5-5
Original file line number
Diff line number
Diff line change
@@ -85,11 +85,11 @@ The following properties are supported in ``qlpack.yml`` files.
85
85
* - ``suites``
86
86
- ``suites``
87
87
- Optional
88
-
- The path to a directory that contains the "well-known" query suites in the pack, defined relative to the pack directory. You can run "well-known" suites stored in this directory by specifying the pack name, without providing their full path. To use query suites stored in other directories in the pack, you must provide their full path. For more information about query suites, see ":doc:`Creating CodeQL query suites <../using-the-codeql-cli/creating-codeql-query-suites>`."
88
+
- The path to a directory that contains the "well-known" query suites in the pack, defined relative to the pack directory. You can run "well-known" suites stored in this directory by specifying the pack name, without providing their full path. To use query suites stored in other directories in the pack, you must provide their full path. For more information about query suites, see ":doc:`Creating CodeQL query suites <creating-codeql-query-suites>`."
89
89
* - ``extractor``
90
90
- ``javascript``
91
91
- All test packs
92
-
- The CodeQL language extractor to use when the CLI creates a database from test files in the pack. For more information about testing queries, see ":doc:`Testing custom queries <../using-the-codeql-cli/testing-custom-queries>`."
92
+
- The CodeQL language extractor to use when the CLI creates a database from test files in the pack. For more information about testing queries, see ":doc:`Testing custom queries <testing-custom-queries>`."
93
93
* - ``tests``
94
94
- ``.``
95
95
- Optional for test packs
@@ -124,7 +124,7 @@ and ``libraryPathDependencies`` properties. If the pack contains query suites, y
124
124
use the ``suites`` property to define their location. Query suites defined
125
125
here are called "well-known" suites, and can be used on the command line by referring to
126
126
their name only, rather than their full path.
127
-
For more information about query suites, see ":doc:`Creating CodeQL query suites <../using-the-codeql-cli/creating-codeql-query-suites>`."
127
+
For more information about query suites, see ":doc:`Creating CodeQL query suites <creating-codeql-query-suites>`."
128
128
129
129
For example, a ``qlpack.yml`` file for a QL pack featuring custom C++ queries
130
130
and libraries may contain:
@@ -154,10 +154,10 @@ For custom QL packs containing test files, you also need to include an
154
154
``extractor`` property so that the ``test run`` command knows how to create test
155
155
databases. You may also wish to specify the ``tests`` property.
156
156
157
-
.. include:: ../../reusables/test-qlpack.rst
157
+
.. include:: ../reusables/test-qlpack.rst
158
158
159
159
For more information about running tests, see ":doc:`Testing custom queries
Copy file name to clipboardExpand all lines: docs/codeql/codeql-cli/index.rst
+3-3
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,12 @@ CodeQL CLI
10
10
11
11
- :ref:`CodeQL CLI reference <codeql-cli-reference>`: Learn more about the files you can use when running CodeQL processes and the results format and exit codes that CodeQL generates.
12
12
13
-
- `CodeQL CLI manual <codeql-cli-manual>`__: Detailed information about all the commands available with the CodeQL CLI.
13
+
- `CodeQL CLI manual <../codeql-cli-manual>`__: Detailed information about all the commands available with the CodeQL CLI.
Copy file name to clipboardExpand all lines: docs/codeql/codeql-language-guides/abstract-syntax-tree-classes-for-working-with-javascript-and-typescript-programs.rst
+3-3
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ Abstract syntax tree classes for working with JavaScript and TypeScript programs
5
5
6
6
CodeQL has a large selection of classes for representing the abstract syntax tree of JavaScript and TypeScript programs.
Copy file name to clipboardExpand all lines: docs/codeql/codeql-language-guides/analyzing-control-flow-in-python.rst
+3-3
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ An annotated flow graph:
32
32
33
33
|Python control flow graph|
34
34
35
-
.. |Python control flow graph| image:: ../../images/python-flow-graph.png
35
+
.. |Python control flow graph| image:: ../images/python-flow-graph.png
36
36
37
37
The simplest use of the ``ControlFlowNode`` and ``AstNode`` classes is to find unreachable code. There is one ``ControlFlowNode`` per path through any ``AstNode`` and any ``AstNode`` that is unreachable has no paths flowing through it. Therefore, any ``AstNode`` without a corresponding ``ControlFlowNode`` is unreachable.
38
38
@@ -119,6 +119,6 @@ Example finding mutually exclusive blocks within the same function
Copy file name to clipboardExpand all lines: docs/codeql/codeql-language-guides/analyzing-data-flow-and-tracking-tainted-data-in-python.rst
+3-3
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Taint tracking differs from basic data flow in that it considers non-value-prese
17
17
For example, in the assignment ``dir = path + "/"``, if ``path`` is tainted then ``dir`` is also tainted,
18
18
even though there is no data flow from ``path`` to ``path + "/"``.
19
19
20
-
Separate CodeQL libraries have been written to handle 'normal' data flow and taint tracking in :doc:`C/C++ <../codeql-for-cpp/analyzing-data-flow-in-cpp>`, :doc:`C# <../codeql-for-csharp/analyzing-data-flow-in-csharp>`, :doc:`Java <../codeql-for-java/analyzing-data-flow-in-java>`, and :doc:`JavaScript <../codeql-for-javascript/analyzing-data-flow-in-javascript>`. You can access the appropriate classes and predicates that reason about these different modes of data flow by importing the appropriate library in your query.
20
+
Separate CodeQL libraries have been written to handle 'normal' data flow and taint tracking in :doc:`C/C++ <analyzing-data-flow-in-cpp>`, :doc:`C# <analyzing-data-flow-in-csharp>`, :doc:`Java <analyzing-data-flow-in-java>`, and :doc:`JavaScript <analyzing-data-flow-in-javascript>`. You can access the appropriate classes and predicates that reason about these different modes of data flow by importing the appropriate library in your query.
21
21
In Python analysis, we can use the same taint tracking library to model both 'normal' data flow and taint flow, but we are still able make the distinction between steps that preserve values and those that don't by defining additional data flow properties.
22
22
23
23
For further information on data flow and taint tracking with CodeQL, see ":ref:`Introduction to data flow <about-data-flow-analysis>`."
@@ -264,6 +264,6 @@ Further reading
264
264
- ":ref:`Exploring data flow with path queries <exploring-data-flow-with-path-queries>`"
0 commit comments