The vanilla-parachain template under templates is currently using relative paths (which means it won't compile). These need to be changed to crates-io dependencies.

Depending on the template chosen, the tool should be able to determine which chain_spec.templ file to modify and write.

If a user instantiates a template using pop create, and then navigates inside the folder and runs pop pallet, we want a default where it detects a pallets/ folder, if not one, create it, and then complete the pallet addition logic. However, there's a one caveat:

How do we know from pop that we are inside a template project?

Among pop pallet <options> there will be an option to take in a --path but we should also provide a quick default that replicates the behaviour described above for a frictionless experience.

Based on the runtime config that's generated, the chainspec must adjust accordingly.

For instance, if the template is generating config for some pallet which expects a genesis_config, the same should reflect in the appropriate chain_spec.templ

Should close #8 before this.

Once it's detected that we are inside a substrate parachain repo, pop pallet will create a pallet that's inert. The user will have to manually install the pallet into their runtime and genesis in order to use it. This brings us to a somewhat of a crossroads.

Q : How should the pallet be installed?
One way would be to generate the AST of runtime and chain_spec code specifically and insert quote! { .. } nodes into it. But this is not easily done with runtime/src/lib.rs because the file makes heavy use of macros already. For the chain_spec.rs file, this solution can be applied. For the runtime however, we would need to scrape the file and edit it in place with the pallet config, benchmarks, and other machinery, while also checking for name collisons.
Then finally, the runtime/Cargo.toml and node/Cargo.toml will have to be updated.

After #8 and #9, we can move on to look for pulling pallets from FRAME directly and having them installed using the same machinery that's implemented for #9.

The current design provides the latest templates. Is it worthwhile to add functionality to create a template at a specific version ?

# example
pop create my-app [email protected]