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
Hi there! We have a monorepo and the inherited from/defined in is not populating properly, it points to a lib location instead of an src location. I saw there is already an issue for this #2416 but having declaration map on still does not help.
The best solution for me would to either have the Inherited from or defined in to be removed, is there a way to do this right now or would i need to create a plugin?
Another solution would be to have the Accessors tab to not generate, as this only happens under accessors.
Thanks
Heres the issue in the docs and a screenshot below: https://docs.web3js.org/libdocs/Contract#inherited-from
Search terms
Expected Behavior
Actual Behavior
Steps to reproduce the bug
Environment
Typedoc version:
TypeScript version:
Node.js version:
OS:
The text was updated successfully, but these errors were encountered:
Inheritance sections would have to be disabled with a plugin
If you're able to set up a minimal reproduction, I can look at why the links aren't showing up -- from a very cursory glance, it looks like you aren't using packages mode, so all the types seem like they would be coming from the initial compilation anyways...
Hi there! We have a monorepo and the inherited from/defined in is not populating properly, it points to a lib location instead of an src location. I saw there is already an issue for this #2416 but having declaration map on still does not help.
The best solution for me would to either have the
Inherited from
ordefined in
to be removed, is there a way to do this right now or would i need to create a plugin?Another solution would be to have the Accessors tab to not generate, as this only happens under accessors.
Thanks
Heres the issue in the docs and a screenshot below:
https://docs.web3js.org/libdocs/Contract#inherited-from
Search terms
Expected Behavior
Actual Behavior
Steps to reproduce the bug
Environment
The text was updated successfully, but these errors were encountered: