lfr create client-extension
It allows you to create a Client Extension from an official sample. Since Client Extensions are under intensive development, they’re not available as templates. So you will need to update the configuration files of any Client Extension you create.
The configuration directory contains the Client Extensions samples. The samples are cloned from a custom repository that mirrors the official samples contained in the monorepo and rename some components to be more intelligible.
Starting with v3.3.0, it also contains unofficial extra samples pushed to this repository, allowing to extend the capabilities of client extensions to new languages and frameworks that are missing from the official samples.
Usage:
lfr create workspace NAME [flags]
# or
lfr c ws NAME [flags]
Running this command with no argument triggers the interactive mode where you can choose the template and enter a name from the terminal (and other options depending on the template). To make the interactive mode accessible, edit the /.lfr/config.toml:
[output]
accessible = true
Examples:
# Some official samples
lfr c cx batch my-batch
lfr c cx custom-element-angular my-angular
lfr c cx custom-element-react-dom my-react
lfr c cx etc-node my-node-microservice
lfr c cx etc-spring-boot my-spring-boot-microservice
lfr c cx site-initializer my-site-initializer
lfr c cx commerce-payment-integration my-payment-connector
# Some extra samples
lfr c cx custom-element-svelte my-svelte-app
lfr c cx etc-golang my-golang-microservice
lfr c cx etc-java-quarkus my-quarkus-microservice
lfr c cx etc-java-vertx my-vertx-microservice
lfr c cx etc-python-fastapi my-python-microservice
Flags:
-h,--help- help for
lfr create client-extension
- help for
Global Flags:
--no-color- disable colors for output messages