split command takes an API description file and creates a multi-file structure out of it by extracting referenced parts into standalone, separate files. The advantage of this approach is making smaller files that are easier to manage and a structure that makes reviewing simpler.
bundle and supply the main file as the entrypoint to get your OpenAPI description in one file. Many OpenAPI tools prefer a single file, but
bundle allow you to manage your files easily for development, and then prepare a single file for other tools to consume.
OpenAPI 3.x only
split command doesn't support OpenAPI 2.0 descriptions.
redocly split <api> --outDir=<path> redocly split [--help] [--version] redocly split --version
|api||string||REQUIRED. Path to the API description file that you want to split into a multi-file structure.|
|--outDir||string||REQUIRED. Path to the directory where you want to save split files. If the specified directory doesn't exist, it is created automatically.|
|--separator||string||File path separator used while splitting. The default value is
|--config||string||Specify path to the config file.|
|--version||boolean||Show version number.|
redocly split pet.yaml --outDir=openapi
Document: pet.yaml is successfully split and all related files are saved to the directory: openapi pet.yaml: split processed in 33ms
openapi directory, the
split command "unbundles" the specified API description. Code samples, components, and paths are split from the root API description into separate files and folders. The structure of the unbundled directory corresponds to the structure created by our openapi-starter tool.