Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

forge doc --build --root <PATH> --prefix not found error #4533

Open
2 tasks done
dalechyn opened this issue Mar 11, 2023 · 3 comments
Open
2 tasks done

forge doc --build --root <PATH> --prefix not found error #4533

dalechyn opened this issue Mar 11, 2023 · 3 comments
Labels
C-forge Command: forge Cmd-forge-doc Command: forge doc T-bug Type: bug

Comments

@dalechyn
Copy link

dalechyn commented Mar 11, 2023

Component

Forge

Have you ensured that all of these are up to date?

  • Foundry
  • Foundryup

What version of Foundry are you on?

forge 0.2.0 (28b2ae6 2023-03-04T00:10:50.272293Z)

What command(s) is the bug in?

forge docs

Operating System

macOS (Intel)

Describe the bug

forge docs subcommand states the support of --root argument.

However, when trying to provide one, the execution fails:
Снимок экрана 2023-03-11 в 21 20 05
Снимок экрана 2023-03-11 в 21 20 16

@dalechyn dalechyn added the T-bug Type: bug label Mar 11, 2023
@oveddan
Copy link

oveddan commented May 4, 2023

I get the same error too, when running the command:
forge doc --build --out ./documentation

@jac18281828
Copy link

I just hit this running the following command:

forge doc --out ./_site 

Interestingly this does not occur when I remove the dot-slash as a workaround:

forge doc --out _site

@nategraf
Copy link

nategraf commented May 14, 2024

In our case, we realized the issue is that the root of our forge project is not the git root. We have the forge project in the ./contracts folder. Our workaround for the issue is to add remappings to the root of the git repository, and then run forge doc for the full repo. This is not ideal, since we may have multiple forge projects in the same repo in the future, and would like the ability to build the docs separately.

https://github.com/risc0/risc0-ethereum/pull/111/files

I spent some time trying to figure out exactly where this error is coming from, but have so far not figured it out. The fact that this mitigation works is some new evidence, but I haven't had a chance yet to re-investigate.

@zerosnacks zerosnacks added A-docs Area: docs C-forge Command: forge Cmd-forge-doc Command: forge doc and removed A-docs Area: docs labels Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-forge Command: forge Cmd-forge-doc Command: forge doc T-bug Type: bug
Projects
No open projects
Status: Todo
Development

No branches or pull requests

5 participants