We should add some docu on recommended setup for working with vim.

https://ihp.digitallyinduced.com/Guide/editors.html

Documentation Feedback

I noticed on the Stencil that two interesting badges are displayed in its README.md files. These two displays easily which version is available in NPM and which licensing is used.

I think we can add these two to our README.md (in any web components, utils, etc.) too.

Code

In Stencil it is solved as following:

`

fetchPypi just calls fetchurl underneath but has a slightly different calling syntax in order to construct the URL. It would be great to track these external dependencies using niv. :-)

Otherwise one might get an error like:

cachix push /nix/store/7i1kqf6x52l1fhqqdmqgggjr0zigggik-cachix-0.1.3/bin/cachix

NoInput "You need to specify store paths either as stdin or as a cli argument"

Currently, we are not able to
a) symbolically execute init code with symbolic arguments
b) get srcmapping for init code with arguments

We could change ContractCode as follows:

data ContractCode
  = InitCode (ByteString, Buffer)    -- ^ "Constructor" code, during contract creation (possibly with arguments)
  | RuntimeCode ByteString           -- ^ "Instance" code, after contract crea

It would be nice to have an easy way of installing bash completions from optparse-applicative.

We've added a small post install script to our own CLI tools with a module like the following:

{pkgs, ...}:
{
    packages.our-pkg-one.components.exes.our-exe-one.build-tools = [ pkgs.installShellFiles ];
    packages.our-pkg-one.components.all.postInstall = pkgs.lib.mkForce "";
    pac