-
Notifications
You must be signed in to change notification settings - Fork 135
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
Errors from paths being shortened twice #23
Comments
tgirardi
added a commit
to tgirardi/jaguarjs-jsdoc
that referenced
this issue
Sep 10, 2014
Prevent doclet paths from being shortened twice. Solve: issue davidshimjs#23 (equivalent to jsdoc/jsdoc#514) Based on: jsdoc/jsdoc@f958ab0
tgirardi
added a commit
to tgirardi/jaguarjs-jsdoc
that referenced
this issue
Sep 10, 2014
Prevent doclet paths from being shortened twice. Solve: issue davidshimjs#23 (equivalent to jsdoc/jsdoc#514) Based on: jsdoc/jsdoc@f958ab0
twidi
pushed a commit
to twidi/jaguarjs-jsdoc
that referenced
this issue
Nov 24, 2014
Prevent doclet paths from being shortened twice. Solve: issue davidshimjs#23 (equivalent to jsdoc/jsdoc#514) Based on: jsdoc/jsdoc@f958ab0
bsvensson
pushed a commit
to bsvensson/jaguarjs-jsdoc
that referenced
this issue
Mar 19, 2015
Prevent doclet paths from being shortened twice. Solve: issue davidshimjs#23 (equivalent to jsdoc/jsdoc#514) Based on: jsdoc/jsdoc@f958ab0
bsvensson
pushed a commit
to bsvensson/jaguarjs-jsdoc
that referenced
this issue
Mar 19, 2015
Prevent doclet paths from being shortened twice. Solve: issue davidshimjs#23 (equivalent to jsdoc/jsdoc#514) Based on: jsdoc/jsdoc@f958ab0
Now the paths don't get shortened at all! This is even worse! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was reported in jsdoc here: jsdoc/jsdoc#514; and solved with the following commit: jsdoc/jsdoc@f958ab0
However, the issue is still present in this template.
I applied the patch in the mentioned commit, to jaguarjs template, and the problem was gone (at least the one I was experiencing in my particular case).
The text was updated successfully, but these errors were encountered: