mryozo16 / jsdoc-toolkit

Automatically exported from code.google.com/p/jsdoc-toolkit
0 stars 0 forks source link

filename overwrite #134

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. have 2 files that are the same name, in different folders

What is the expected output? What do you see instead?
The source file has the same name for both files, so thus one of the source
file overrides the other one.

What version of the product are you using? On what operating system?
1.4

Please provide any additional information below.
Essentially the error is that if you have 2 files with the same name, but
each is in a different folder, then the jsdoc toolkit will not have 2
different source files, but rather only 1 (because the naming convetion is
filename.src.js)

Original issue reported on code.google.com by mou...@gmail.com on 5 May 2008 at 7:33

GoogleCodeExporter commented 8 years ago
I can't reproduce this, but I probably don't understand what problem you're
describing. The name of the source file is not related in any way to the 
variables
defined within them (as far as JsDoc Toolkit is concerned). If the *variable 
names*
were the same in multiple files then yes, the later ones will overwrite the 
earlier
ones. Is that what you mean?

Otherwise if you can provide the simplest possible demonstration of this 
problem by
attaching a zipped collection of files, I'll try to reproduce the problem with 
that.

Original comment by micmath on 5 May 2008 at 9:31

GoogleCodeExporter commented 8 years ago
What I'm referring to, is the 'defined in filename.js' source path given on the 
docs
(this is the {+thisClass.source+} definition.

So if you have the following structure

/scripts/fold1/file.js
/scripts/fold2/file.js

Now, you have 2 js files with the same name, but in different folders. If you 
run the
toolkit on the scripts folder, you will get the 'class defined in LINK' , where 
LINK
points to the .src.html
Now, I dont think the toolkit makes the .src.html files unique, but rather uses 
the
filename, so thus it will create two file.src.html, but 1 will be over-written 
from
the other one, and thus it wont show the correct 2 different files.

Original comment by mou...@gmail.com on 6 May 2008 at 6:09

GoogleCodeExporter commented 8 years ago
Can you provide the name of the template you are referring to and the 
commandline you
are using please.

Original comment by micmath on 6 May 2008 at 6:21

GoogleCodeExporter commented 8 years ago
well the template I noticed it on was oldenglish
command line was the following format:
java -jar app/js.jar app/run.js -r -a -p -t=templates/oldenglish FOLDERNAME -v

Original comment by mou...@gmail.com on 6 May 2008 at 6:23

GoogleCodeExporter commented 8 years ago
Ok, so the reason I can't reproduce the problem is because I'm not using the
oldenglish template. If you find that this problem occurs with one of the 
templates
I've written you can file that here, but if it is specific to oldenglish you 
should
file a bug report with the author of that template (I'm not sure what his email
address is, but check his website perhaps).

Original comment by micmath on 6 May 2008 at 7:14

GoogleCodeExporter commented 8 years ago
I will try it with another template in a minute, but I assumed the template 
isnt what
defines the source filenames etc. I will check later and let you know.

Original comment by mou...@gmail.com on 6 May 2008 at 7:47

GoogleCodeExporter commented 8 years ago
Look in oldenglish/publish.js for these lines:

    var file_basename = basename(fileGroup.files[i].filename);
    var file_srcname = file_basename+".src.html";

This is an issue with the template, not JsDoc Toolkit.

Original comment by micmath on 6 May 2008 at 8:11