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
An API is less likely to change than its implementation. Unless developers hook their commits to generating & publishing the API, the prettyfied source code gets out of date. Hence, readers of API would benefit, if for GitHub-hosted projects the API would link to prettyfied source code on GitHub. Could you add an option for that, please.
Additionally, users may want to run jsdoc-baseline on several related projects together. Therefore it should be configurable with a mapping {local-source-code-folder: GitHub URL prefix} to point across multiple GitHub projects.
Ideally, could you make the pretty-source-code pointing code extensible, so this could also work for BitBucket or GitLab.
(I looked at jsdoc-baseline, but I don't know where to start with this - whether in linkToLine() or elsewhere.)
The text was updated successfully, but these errors were encountered:
Hi Jeff,
An API is less likely to change than its implementation. Unless developers hook their commits to generating & publishing the API, the prettyfied source code gets out of date. Hence, readers of API would benefit, if for GitHub-hosted projects the API would link to prettyfied source code on GitHub. Could you add an option for that, please.
Additionally, users may want to run jsdoc-baseline on several related projects together. Therefore it should be configurable with a mapping {local-source-code-folder: GitHub URL prefix} to point across multiple GitHub projects.
Ideally, could you make the pretty-source-code pointing code extensible, so this could also work for BitBucket or GitLab.
(I looked at jsdoc-baseline, but I don't know where to start with this - whether in linkToLine() or elsewhere.)
The text was updated successfully, but these errors were encountered: