From ab2d9e9237a828851cb593eca9dd5935191fccb6 Mon Sep 17 00:00:00 2001 From: joshmossas Date: Wed, 7 Aug 2024 11:02:54 -0500 Subject: [PATCH] notes --- docs/implementing-an-arri-server.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/implementing-an-arri-server.md b/docs/implementing-an-arri-server.md index dde3c627..f8c32d4e 100644 --- a/docs/implementing-an-arri-server.md +++ b/docs/implementing-an-arri-server.md @@ -196,7 +196,7 @@ arri codegen https://myapi.com/__definition # http endpoint ## Bonus: Create a plugin for the Arri CLI -Server plugins dictate what happens when you run `arri dev` and `arri build`. +Server plugins dictate what happens when you run `arri dev` and `arri build`. By creating a plugin you can create a fully automated experience. In order to create a server plugin use the `defineServerConfig` helper from the `arri` package: @@ -267,7 +267,7 @@ Let's say we've configured a go generator that reads our go application and outp const goServer = defineServerConfig({ devArgs: {}, devFn(_, generators) { - // run go generate + // run "go generate" execSync("go generate", { stdio: "inherit", }); @@ -277,7 +277,7 @@ const goServer = defineServerConfig({ ) as AppDefinition; // run all of the registered Arri generators await Promise.all(generators.map((item) => item.generator(appDef))); - // start run application + // start the go application execSync("go run main.go", { stdio: 'inherit' });