Collins Muriuki

> I ought to link more to them from this page though. Fair enough, the links should suffice then

Hi @guillemcordoba I would like some clarification just to better understand your proposal. At the moment, the repositories scaffolded to be used as modules rather than webhapps still contain a...

> What would hc scaffold module do? I'm seeking a better understanding on whether it's still appropriate to use `hc scaffold web-app` to scaffold a module instead of a web...

> But why would we need to keep the dna.yaml and happ.yaml files? I agree with the decision to no longer require the `dna.yaml` and `happ.yaml` files for these kind...

I see, this is quite new to me I am curious to know how the proposed method is different from what I have used before from [this guide](https://holochain-open-dev.github.io/profiles/?path=/docs/introduction--docs). Do they...

> So in the repository where the zome lives, there is no happ.yaml or dna.yaml but you can still test your app. Also another question regarding this; the fake manifests...

I see, so for such repos, the scaffolding tool should not be generating these manifest files, this is the only change required from the cli as far as I understand....

> What I'd like to change is that in repos where there's no dna.yaml, only zomes, I can't run hc scaffold entry-type or hc scaffold link-type. I see, so for...

Great, I can add this functionality, probably as an optional flag passed to `hc scaffold web-app` to indicate this is a module.

> The problematic code is [here](https://github.com/holochain/scaffolding/blob/e9f3db78b7ee1c858b29a2b1f65ff05e90b97661/src/cli.rs#L560). Yes, this change will also be made, I am just considering the user who scaffolds a web-app that is intended to be used as...