You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, in projects with "legacy" configuration (no {hex, [{doc, ...}]} configuration the following output is generated when running rebar3 hex and rebar3 hex docs:
$ rebar3 hex docs
===> Verifying dependencies...
===> No valid hex docs configuration found. Docs will will not be generated
Local Password:
===> Published docs for grisp 2.0.0-rc1
I think it is confusing because the "No valid hex docs..." line is red and seems to indicate an error, an then the docs are published anyway (most likely stale since the plug-in will no longer re-generate the docs without the correct undocumented configuration).
The text was updated successfully, but these errors were encountered:
Right, what we can do here for v6.11.x is check to see if there's doc provider config, but then also check to see if there's a doc dir with at least an index file in it, if so, then don't warn.
Likewise, we should omit "Published docs..." if either of the above don't hold true.
Currently, in projects with "legacy" configuration (no
{hex, [{doc, ...}]}
configuration the following output is generated when runningrebar3 hex
andrebar3 hex docs
:I think it is confusing because the "No valid hex docs..." line is red and seems to indicate an error, an then the docs are published anyway (most likely stale since the plug-in will no longer re-generate the docs without the correct undocumented configuration).
The text was updated successfully, but these errors were encountered: