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
When trying to run npm run storybook and compoDoc is enable, then it fails to parse the resolve object on routes.
Routes parsing error, maybe a trailing comma or an external variable, trying to fix that later after sources scanning.
This is my file that fails to parse (If I remove the resolve attribute then it works)
`
import {inject, NgModule} from '@angular/core';
import {RouterModule, Routes} from '@angular/router';
import {PersonListComponent} from './person-list/person-list.component';
import {AuthGuard} from '../_helpers/auth.guard';
import {PersonListResolver} from './person-list/person-list.resolver';
const routes: Routes = [
{
path: '',
component: PersonListComponent,
canActivate: [AuthGuard],
resolve: {
'personListLink': () => inject(PersonListResolver).resolvePersonListLink()
}
}
];
@NgModule({
imports: [RouterModule.forChild(routes)],
exports: [RouterModule]
})
export class PeopleRoutingModule {
}
`
Current versions
1.1.23
TypeScript version used by Compodoc : 5.2.2
TypeScript version of current project : 5.0.2
Node.js version : v18.19.0
Operating system : Windows 10
The text was updated successfully, but these errors were encountered:
vogloblinsky
changed the title
CompoDoc failing to parse or generate the documentation
[BUG] CompoDoc failing to parse or generate the documentation
Mar 21, 2024
When trying to run npm run storybook and compoDoc is enable, then it fails to parse the resolve object on routes.
Routes parsing error, maybe a trailing comma or an external variable, trying to fix that later after sources scanning.
This is my file that fails to parse (If I remove the resolve attribute then it works)
`
`
Current versions
1.1.23
TypeScript version used by Compodoc : 5.2.2
TypeScript version of current project : 5.0.2
Node.js version : v18.19.0
Operating system : Windows 10
The text was updated successfully, but these errors were encountered: