#Ok Thanks Erik So do I need to write

1 messages · Page 1 of 1 (latest)

plucky nest
#

Writing an extension is probably not necessary to start out here. I think the simplest way to start right now would be to write a script for each out the steps you want to support (tidy and build), just with one of the languages we currently support (javascript/typescript or go). There's an example in javascript here: https://github.com/dagger/todoapp/blob/cloak/scripts/kick-the-tires/index.mjs

#

There, the local source code is loaded up into a container and then yarn command are run on top of it. In your case, you'd do something similar except with running go commands.

#

At the end you will want to export the result of the commands back to your local dir, which can be done using a query something like this:

{ 
  host {
    workdir {
      write(path: "some/subpath", contents: $some_fs_id)
    }
  }
}
#

So while it will be a bit verbose, I think you can accomplish your goal with just a script.

Extensions are useful once you start wanting to re-use existing code, similar to how you can re-use libraries rather than implement everything yourself. But since we don't yet have a pre-built go extension for you to re-use, it's probably best to just start with a script.

rapid scaffold
#

Great. It is clear for me now.

rapid scaffold
#

Hi. I'm trying to write my script but the go sdk seems not to have the same interfaces like the typescript one .

#

I'm looking for something similar to client.request in the typescript sdk

plucky nest
rapid scaffold
#

I can’t access the file. I think the repo is private @plucky nest

rapid scaffold