codeql/misc/codegen
Paolo Tranquilli 19bb8fe22d Bazel: use bzlmod 2024-02-12 10:55:40 +01:00
..
generators Codegen: add `internal` to properties, rename `ql_internal->internal` 2023-11-24 06:56:55 +01:00
lib Codegen: remove unneeded `has_description` property 2023-11-24 06:56:55 +01:00
loaders Codegen: fix python compatibility problem 2023-10-23 16:56:44 +02:00
templates Codegen: add internal QLdoc to property templates 2023-11-24 06:56:55 +01:00
test Codegen: remove unneeded `has_description` property 2023-11-24 06:56:55 +01:00
.pep8 Move `swift/codegen` to `misc/codegen` 2023-02-27 09:46:48 +01:00
BUILD.bazel Move `swift/codegen` to `misc/codegen` 2023-02-27 09:46:48 +01:00
README.md Codegen: update `README.md` files 2023-02-27 10:01:50 +01:00
codegen.py Codegen: mark generated checked in files as such 2023-05-05 09:29:16 +02:00
requirements_in.txt Bazel: use bzlmod 2024-02-12 10:55:40 +01:00
requirements_lock.txt Bazel: use bzlmod 2024-02-12 10:55:40 +01:00

README.md

Code generation suite

This directory contains the code generation suite used by the Swift extractor and the QL library. This suite will use the abstract class specification of schema.py to generate:

An example schema.py can be found in the Swift package.

Usage

By default bazel run //misc/codegen -- -c your-codegen.conf will load options from your-codegen.conf. See the Swift configuration for an example. Calling misc/codegen/codegen.py directly (provided you installed dependencies via pip3 install -r misc/codegen/requirements.txt) will use a file named codegen.conf contained in an ancestor directory if any exists.

See bazel run //misc/codegen -- --help for a list of all options. In particular --generate can be used with a comma separated list to select what to generate (choosing among dbscheme, ql, trap and cpp).

Implementation notes

The suite uses mustache templating for generation. Templates are in the templates directory, prefixed with the generation target they are used for.

Rather than passing dictionaries to the templating engine, python dataclasses are used as defined in the lib directory. For each of the four generation targets the entry point for the implementation is specified as the generate function in the modules within the generators directory.

Finally, codegen.py is the driver script gluing everything together and specifying the command line options.

Unit tests are in the test directory and can be run via bazel test //misc/codegen/test.

For more details about each specific generation target, please refer to the module docstrings in the generators directory.