pub struct GenerateBuilder { /* private fields */ }
Expand description
The configuration for pavex
’s generate
command.
You can use Client::generate
to start building the command configuration.
Implementations§
source§impl GenerateBuilder
impl GenerateBuilder
sourcepub fn execute(self) -> Result<(), GenerateError>
pub fn execute(self) -> Result<(), GenerateError>
Generate the runtime library for the application.
This will invoke pavex
with the chosen configuration.
It won’t return until pavex
has finished running.
If pavex
exits with a non-zero status code, this will return an error.
sourcepub fn command(self) -> Result<Command, BlueprintPersistenceError>
pub fn command(self) -> Result<Command, BlueprintPersistenceError>
Assemble the std::process::Command
that will be used to invoke pavex
,
but do not run it.
It will persist the blueprint to a file, though.
This method can be useful if you need to customize the command before running it.
If that’s not your usecase, consider using GenerateBuilder::execute
instead.
sourcepub fn diagnostics_path(self, path: PathBuf) -> Self
pub fn diagnostics_path(self, path: PathBuf) -> Self
Set the path to the file that Pavex will use to serialize diagnostic information about the application.
Diagnostics are primarily used for debugging the generator itself.
If this is not set, Pavex will not persist any diagnostic information.