Bug: double forward slash causes graph generation error

[flashdave1973]

Should double forward slashes be treated as a single line comment?

I believe this causes a previously referenced graph error.

[flashdave1973]

in any event lines 18 & 20 - 26 should not be commented out

[vogloblinsky]

@flashdave1973 how did you install compodoc ? npm or yarn ?
what is your environment ?
i just added this code in the ng2 demo project, and generate the doc on mac without problem :

import {
    Pipe,
    PipeTransform
} from '@angular/core';
import * as moment from 'moment';

@Pipe({
    name: 'dateDisplayFormat'
})

/**
 * implementation of DateDisplayFormatPipe : format birth date values for display in UI
 */

export class DateDisplayFormatPipe implements PipeTransform {
    transform(value: string) : string {
        // is defined ?
        if (value) {
            // TODO: replace with angular2localization implementation later
            return moment(value).locale('en-US').format('M/DD/YYYY');
        } else {
            return 'NA';
        }
    }
}

[flashdave1973]

I am on windows 7, Installed with npm v4.0.5 & node v6.9.1. The only error I get is the graph error. However every component, service, module, pipe or any other file that contains a double quoted comment.... the docs comment out ever line there after.

[flashdave1973]

So it looks like I have 2 issues... I may have found the culprit behind one of them.....

the erros in the console screenshot points to an invalid path...
C:\inetpub\NodeJsServer\LogistiCAD\LogistiCAD Web UI is the actual path to my project... however the error does not show the complete path.... seems it does not like the space in my folder name

[flashdave1973]

Update: removed the spaces in my project path folder and I am no longer getting an Error during graph generation.

Having noticed // unsupported comment, ill go ahead and close this ticket

[vogloblinsky]

@flashdave1973 bug reproduced with spaces in project path on windows, issue here

[lock]

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.