Closed farhadi closed 2 years ago
So, the reason it's required is because someone can define a doc provider on a per repository basis. That said, I think what we can do is check to see if there are
If 1 and 2 hold true, raise an error instructing the user to provide a repo argument, otherwise, continue.
We are using
rebar3 hex build
command to build packages for our self-hosted hex repo, but since we have multiple repos defined in rebar.config,rebar3 hex build
complains that "A repository argument is required", but since build command only builds the package and doesn't publish it to the repo, I think this repo argument can be removed from build command, right?