[BUG] : graph generation error with spaces in folder path about compodoc HOT 21 CLOSED

still seeing this error on release 0.0.31

from compodoc.

Ok, reproduced. My last test was with compodoc installed globally, and not locally.

from compodoc.

@vogloblinsky First, Thank you so much for the tool, it is great, especially with the addition of the coverage hurry to that.
The only problem is that I still get this:

Error during graph generation: : 'C:\Program Files ' is not recognized as an internal or external command,
operable program or batch file.

"compodoc": "0.0.33", installed both globally and locally.

Thanks again for the hard work

from compodoc.

Can i have more information about your context ?
Versions etc ?

from compodoc.

npm 3.10.6
node 5.5.0
angular 2.4.1
typescript 2.1.4
compodoc 0.0.33 (installed globally and locally)
path C:\Program Files (x86)\Jenkins\workspace\myProject (Notice the space in the path)

I think issue is the special characters in the path.

from compodoc.

Ok thanks reproduced.

from compodoc.

I'm still getting this error with 0.0.34
If installed globally AND locally I get:

Error during graph generation: : 'C:\Program Files ' is not recognized as an internal or external command,
operable program or batch file.

If installed globally only I get: (issue #65)
Error during graph generation: : The system cannot find the path specified.

If installed Locally only I get:

Error during graph generation: : 'C:\Program Files ' is not recognized as an internal or external command,
operable program or batch file.

from compodoc.

@vogloblinsky any news with this bug.

from compodoc.

Reproduced in my VM Windows, try to fix it this afternoon.

from compodoc.

@vogloblinsky thanks man I appreciate that.
Merci.

from compodoc.

Fixed in 0.0.38

from compodoc.

@vogloblinsky sorry to say this but I still get the same errors with --version 0.0.38

from compodoc.

@nadhir-falta
Ok.
Could you re-test by using angular-cli, generate a fresh project in C:\Program Files (x86)\Jenkins\workspace\
and run compodoc on it : compodoc -p src/tsconfig.json -s
Thanks

from compodoc.

@vogloblinsky I tried that and that's what I get:

### [10:06:05] parsing        : C:/Program Files (x86)/Jenkins/workspace/PFM-UI-Docs/TestCompodoc/src/environments/environment.prod.ts
[10:06:06] parsing        : C:/Program Files (x86)/Jenkins/workspace/PFM-UI-Docs/TestCompodoc/src/environments/environment.ts
[10:06:06] parsing        : C:/Program Files (x86)/Jenkins/workspace/PFM-UI-Docs/TestCompodoc/src/main.ts
[10:06:08] parsing        : C:/Program Files (x86)/Jenkins/workspace/PFM-UI-Docs/TestCompodoc/src/polyfills.ts
[10:06:11] parsing        : C:/Program Files (x86)/Jenkins/workspace/PFM-UI-Docs/TestCompodoc/src/test.ts
[10:06:12] Prepare modules
[10:06:12] Prepare components
[10:06:12] Process documentation coverage report
[10:06:12] Process pages
[10:06:12] Process page   : index
[10:06:12] Process page   : overview
[10:06:12] Process page   : modules
[10:06:12] Process page   : AppModule
[10:06:12] Process page   : AppComponent
[10:06:12] Process page   : coverage
[10:06:12] Copy main resources
[10:06:12] Process main graph
[10:06:12] Error during graph generation: : The system cannot find the path specified.

from compodoc.

Ok, can i have all your configuration ?
OS, node/npm versions, compodoc global ?
Thanks

from compodoc.

npm 3.10.6
node 5.5.0
angular 2.4.1
typescript 2.1.4
compodoc 0.0.38 (installed globally and locally)
path C:\Program Files (x86)\Jenkins\workspace\myProject

from compodoc.

@vogloblinsky any news about this one ?

from compodoc.

Yes, we have integrated ngd inside @compodoc scope on npm, and last version 0.0.39 doesn't call ngd with a cli call.
Could you upgrade and made a new test ? it works fine on my windows VM inside C:\Program Files (x86)\www\test

from compodoc.

@vogloblinsky Yessss, it is fixed now.
Thank you so much for all this.
Great job on building this tool.

from compodoc.

👍 😃

from compodoc.

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. Why locking ? Having issues with the most up-to-date context.

from compodoc.