Skip to main content

Configure Code Generation

Understanding apex configuration

An apex configuration is YAML that defines which files are generated and by which module. The structure of configuration file is conveyed in Apexlang and JSON schema below.

namespace "apexlang.config.v1"

"The top level elements of the configuration."
type Configuration {
"The path to the apex specification file."
schema: string,
"Global configuration settings available to all targets (optional)."
config: {string: any}?,
"The map of target files to generate and their settings."
generates: {string: Target}

"The configuration for how a target file is generated."
type Target {
"The TypeScript module containing the visitor class."
module: string,
"The name of the exported visitor class that generates the file contents."
visitorClass: string,
"When true, the file is only generated if it does not exist. This is useful for scafolded files."
ifNotExists: bool = false,
"Target-level configuration (optional)."
config: {string: any}?
"Commands to execute that relate to this target (e.g., other code generation tools)."
runAfter: [Command]?

"A command to execute after code generator."
type Command {
"The command to execute."
command: string
"The working directory (optional - default is the current directory)."
dir: string?

Create your first apex.yaml configuration

A common task with regard to API and microservice development is sharing OpenAPI and gRPC specifications with other teams. In this next step, we will generate the specifications for our URL Shortener service. In the root of your urlshortener directory, create a file named apex.yaml:

spec: apex.axdl
module: ''
visitorClass: OpenAPIV3Visitor
module: ''
visitorClass: ProtoVisitor
go_package: ''

Using config, ifNotExists, and runAfter will be demonstrated later in this tutorial.