gelx_cli
A command-line interface for
gelxto generate fully typed Rust code from your Gel schema and query files.
Installation
The gelx_cli is distributed as part of the gelx workspace. To use it, you can build the workspace and then run the gelx binary from the target directory, or install it using cargo:
Alternatively, you can install it directly from the github repo:
Ensure your Gel instance is running and accessible, as the CLI needs to connect to it to introspect the schema and query types.
Global Options
--cwd <path>: Specifies a working directory to run the command from. If provided,gelxwill change to this directory before performing any operations. This is useful if you are invokinggelxfrom a directory different from your project's root.
Usage
The gelx CLI tool generates Rust code from .edgeql files located in your project. It reads configuration from your crate's Cargo.toml file, specifically under the [package.metadata.gelx] section.
Commands
gelx generate
This command generates Rust code based on your .edgeql query files and the Gel schema.
-
Navigate to your crate's root directory:
-
Run the generate command:
The CLI will:
- Read configuration from
[package.metadata.gelx]in yourCargo.toml. - Scan the directory specified by
queries(default:./queries) for.edgeqlfiles. - Connect to your Gel instance to get type information for each query.
- Generate corresponding Rust modules.
- Write the combined code to the file specified by
output_file(default:./src/gelx_generated.rs).
- Read configuration from
gelx check
This command verifies if the currently generated code is up-to-date with your schema and query files. It's useful for CI pipelines to ensure that code generation has been run after any changes.
-
Navigate to your crate's root directory:
-
Run the check command:
The CLI will:
- Perform the same generation process as
gelx generatein memory. - Compare the newly generated code with the content of the existing
output_file. - If they match, it will exit successfully (status code 0).
- If they differ, it will print an error message and exit with a non-zero status code, indicating that
gelx generateneeds to be run.
- Perform the same generation process as
Configuration
The gelx CLI reads its configuration from the Cargo.toml file of the crate it is being run in. The configuration should be placed under the [package.metadata.gelx] table.
Example Cargo.toml configuration:
[]
## The location of the queries relative to the root of the crate.
= "./queries"
## The features to enable and their aliases. By default all features are enabled.
## To disable a feature set it to false. The available features are:
## - query
## - serde
## - strum
## - builder
= { = "ssr", = "ssr", = "ssr" }
## The location of the generated code when using the `gelx` cli.
= "./src/gelx_generated.rs"
## The name of the arguments input struct. Will be transformed to PascalCase.
= "Input"
## The name of the exported output struct for generated queries. Will be transformed to PascalCase.
= "Output"
## The name of the query function exported.
= "query"
## The name of the transaction function exported.
= "transaction"
## The relative path to the `gel` config file. This is optional and if not provided the `gel`
## config will be read from the environment variables.
# gel_config_path = "./gel.toml"
## The name of the `gel` instance to use. This is optional and if not provided the environment
## variable `$GEL_INSTANCE` will be used.
# gel_instance = "$GEL_INSTANCE"
## The name of the `gel` branch to use. This is optional and if not provided the environment
## variable `$GEL_BRANCH` will be used.
# gel_branch = "$GEL_BRANCH"
Refer to the main gelx crate readme.md for more details on the core library and its features.
Contributing
This crate is part of the gelx workspace. Please refer to the main project's contributing guide for details on how to set up the development environment and contribute.
License
Unlicense, see the license file in the root of the workspace.