Currently, with #204, the new "split" edition of the repository structure may only really be used & tested within the docker component, as the monorepo's gno tool does not correctly use replace directives when determining where to gather its imports.
Once that is added to the monorepo, we can update instructions accordingly and suggest a proper development workflow which doesn't need anything other than the gno tool, and possibly soon the gnodev tool.
Currently, with #204, the new "split" edition of the repository structure may only really be used & tested within the docker component, as the monorepo's
gno
tool does not correctly usereplace
directives when determining where to gather its imports.Once that is added to the monorepo, we can update instructions accordingly and suggest a proper development workflow which doesn't need anything other than the
gno
tool, and possibly soon thegnodev
tool.