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-language-guides/data-extensions-to-model-java-dependencies.rst
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
Customizing library models for Java and Kotlin
4
4
==============================================
5
5
6
-
You can use data extensions to model the methods and callables that control data flow in any framework or library. This is especially useful for custom frameworks or niche libraries, that are not supported by the standard CodeQL libraries.
6
+
You can model the methods and callables that control data flow in any framework or library. This is especially useful for custom frameworks or niche libraries, that are not supported by the standard CodeQL libraries.
7
7
8
8
.. include:: ../reusables/kotlin-beta-note.rst
9
9
@@ -12,9 +12,9 @@ You can use data extensions to model the methods and callables that control data
12
12
About this article
13
13
------------------
14
14
15
-
This article contains reference material about how data extensions interact with standard queries and the syntax used to define extensions.
15
+
This article contains reference material about how to define custom models for sources, sinks and flow summaries for Java dependencies in data extension files.
16
16
17
-
If you want to create your own data extensions, you should use the CodeQL model editor in the CodeQL extension for Visual Studio Code. The model editor automatically guides you through the process of defining models, displaying the properties you need to define and the options available. You can save the resulting models as data extensions and use them without worrying about the syntax.
17
+
The best way to create your own models is using the CodeQL model editor in the CodeQL extension for Visual Studio Code. The model editor automatically guides you through the process of defining models, displaying the properties you need to define and the options available. You can save the resulting models as data extension files in CodeQL model packs and use them without worrying about the syntax.
18
18
19
19
For more information, see ":ref:`Using the CodeQL model editor <using-the-codeql-model-editor>`."
20
20
@@ -56,7 +56,7 @@ Publish data extension files in a CodeQL model pack to share
56
56
57
57
You can group one or more data extention files into a CodeQL model pack and publish it to the GitHub Container Registry. This makes it easy for anyone to download the model pack and use it to extend their analysis. For more information, see "`Creating a CodeQL model pack <https://docs.github.com/en/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/creating-and-working-with-codeql-packs#creating-a-codeql-model-pack/>`__ and `Publishing and using CodeQL packs <https://docs.github.com/en/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/publishing-and-using-codeql-packs/>`__ in the CodeQL CLI documentation.
58
58
59
-
Extensible predicates in the CodeQL library for Java/Kotlin
59
+
Extensible predicates used to create custom models in Java and Kotlin
The CodeQL library for Java and Kotlin analysis exposes the following extensible predicates:
@@ -68,7 +68,7 @@ The CodeQL library for Java and Kotlin analysis exposes the following extensible
68
68
69
69
The extensible predicates are populated using data extensions specified in YAML files.
70
70
71
-
Examples of data extension definitions
71
+
Examples of custom model definitions
72
72
--------------------------------------
73
73
74
74
The examples in this section are taken from the standard CodeQL Java query pack published by GitHub. They demonstrate how to add tuples to extend extensible predicates that are used by the standard queries.
0 commit comments