Skip to content

fix(docs): associate each contract with its own artifact - #706

Closed
fengxueweilai wants to merge 1 commit into
aragon:mainfrom
fengxueweilai:my_feature
Closed

fengxueweilai wants to merge 1 commit into
aragon:mainfrom
fengxueweilai:my_feature

Conversation

@fengxueweilai

@fengxueweilai fengxueweilai commented Oct 23, 2026 •

Copy link
Copy Markdown

Description

Fixes #707

Foundry emits a separate artifact for each contract while including the complete source AST in each one. The docs loader associates every contract node with every artifact, so a source containing two contracts can lose one contract or use the wrong documentation metadata.

Only associate a ContractDefinition with the artifact whose filename matches the contract name. Add a fixture with two contracts sharing one source AST and distinct devdoc metadata.

Signed-off-by: fengxueweilai <fengxueweilai@outlook.com>
@fengxueweilai

Copy link
Copy Markdown
Author

Hi @brickpop, would you mind taking a look at this PR when you have a chance?

It touches the current Foundry-based project structure, so I thought you might be the right person to ask. The change itself is kept small and isolated. Happy to revise it if there’s a better way to fit the current OSx structure. Thanks!

@brickpop

Copy link
Copy Markdown
Contributor

Hi @fengxueweilai, thank you for contributing :)

Your PR landed exactly at the point where we start retiring each repo's individual documentation, in favor of the unified knowledge base:

Unfortunately, the PR cannot land here, as /docs will be removed altogether.
Can you let me know if the ABI section under protocol-docs includes what you need?

@brickpop brickpop closed this Oct 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs loader loses contracts declared in the same Solidity source

2 participants