-
**Github username:** --
**Twitter username:** --
**Submission hash (on-chain):** 0x7f6596188339c26af13bdeba3e5bc55f0a8151cda5f655a5afe5bb8028be8386
**Severity:** low
**Description:**
**Description**…
-
Hello, Good day @Czar102!
I saw your post on [Twitter](https://x.com/_czar102/status/1852383023695540343?s=46&t=7dg-o42TflukP9WjESg9VQ), I am interested in the Solidity Developer role and I'm happy…
-
**Github username:** @Jelev123
**Twitter username:** zhulien_zhelev
**Submission hash (on-chain):** 0x6f3596e3cb85812fa2800100a5679f5e574d2e69747f80190a28745de6bd0fb9
**Severity:** low
**Description…
-
It would be very useful if we could also parse natspec comments.
-
## Description and context
Go through core EVM contracts and improve natspec documentation for public functions.
## Definition of done
Docs are in a state where `forge doc` can auto-generate docu…
-
Currently, the protocol contract documentation is maintained manually. However, this is not ideal because it can get out of sync with changes in the code base, and there is delayed feedback for the de…
aiman updated
2 weeks ago
-
### Component
Forge
### Describe the feature you would like
For repositories that declare all Natspec at the interface level and inherit and override all functions, it would be nice to be able to p…
-
To align the NatSpec with the terminology used in our PR and documentation site, we should refactor all references to 'assets' to say 'tokens' instead.
-
Is there a VSCode extension that you would recommend apart from "VS Code Solidity comments"?
Main thing I'm wondering is if there is a way to click "@dev" and see the documentation pop up in a url …
-