Skip to content

Commit 2e99583

Browse files
author
james
committed
fix link
1 parent 81a9ce2 commit 2e99583

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

docs/codeql/writing-codeql-queries/debugging-data-flow-queries-using-partial-flow.rst

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,7 @@ You can try to debug the potential problem by following the steps described belo
3838
Checking sources and sinks
3939
--------------------------
4040

41-
Initially, you should make sure that the ``source`` and ``sink`` definitions contain what you expect. If either the ``source`` or ``sink`` is empty then there can never be any data flow. The easiest way to check this is using quick evaluation in CodeQL for VS Code. Select the text ``node instanceof MySource``, right-click, and choose "CodeQL: Quick Evaluation". This will evaluate the highlighted text, which in this case means the set of sources. For more information, see :ref:`Analyzing your projects <
42-
.. _running-a-specific-part-of-a-query-or-library>` in the CodeQL for VS Code help.
41+
Initially, you should make sure that the ``source`` and ``sink`` definitions contain what you expect. If either the ``source`` or ``sink`` is empty then there can never be any data flow. The easiest way to check this is using quick evaluation in CodeQL for VS Code. Select the text ``node instanceof MySource``, right-click, and choose "CodeQL: Quick Evaluation". This will evaluate the highlighted text, which in this case means the set of sources. For more information, see :ref:`Analyzing your projects <running-a-specific-part-of-a-query-or-library>` in the CodeQL for VS Code help.
4342

4443
If both source and sink definitions look good then we will need to look for missing flow steps.
4544

0 commit comments

Comments
 (0)