prism compile is used to parse the tasks.ref(...) calls, construct the DAG, and generate the manifest.
Usage: prism compile [OPTIONS]
Parse the tasks.ref(...) calls, construct the DAG, and generate the manifest.
Examples:
• prism compile
• prism compile -l debug
â•â”€ Options ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ --log-level -l [info|warn|error|debug] Set the log level │
│ --full-tb Show the full traceback when an error occurs │
│ --help Show this message and exit. │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Here's what prism compile does under the hood.
Parses the tasks contained in the modules/ folder for tasks.ref(...) calls.
It then takes these function calls and creates the dependency graph. You can visualize this graph using the command.
It stores the project metadata (e.g., the configuration, the tasks.ref(...) calls, the targets, and the ) in a manifest.
Example
Here's what the output will look like in Terminal:
$ prism compile
--------------------------------------------------------------------------------
<HH:MM:SS> | INFO | Running with prism v0.2.2...
<HH:MM:SS> | INFO | Found project directory at /Users/my_first_project
<HH:MM:SS> | INFO | RUNNING EVENT 'task DAG'................................................................ [RUN]
<HH:MM:SS> | INFO | FINISHED EVENT 'task DAG'............................................................... [DONE in 0.01s]
<HH:MM:SS> | INFO | Done!
--------------------------------------------------------------------------------
