AngularDoc / angulardoc.github.io

angulardoc.github.io web site
https://angulardoc.github.io
34 stars 1 forks source link

AngularDoc keeps analysing #1

Closed CumpsD closed 7 years ago

CumpsD commented 7 years ago

I've installed AngularDoc VS Code extension, and when I click the AngularDoc item at the bottom, I login and it keeps on analysing. After closing VS Code and re-opening, I get the AngularDoc tab, with an empty Overview and no content.

The content of my angulardoc.json is:

{
  "repoId": "fbea66c1-b772-4a0d-abbc-c4fa5ba41b8c",
  "lastSync": 1481113468630,
  "directoryFilter": [
    "!typings",
    "!node_modules",
    "!.vscode"
  ],
  "fileFilter": [
    "**/!(*.*spec).ts"
  ]
}

Is there any documentation on this file? Maybe I need to help it out to find my application root?

agiledigits commented 7 years ago

Perhaps you can try setting "lastSync" to 0 to make the analyzer re-process all the files.

CumpsD commented 7 years ago

When I try that, it doesnt re-process all the files, it simply gives me an empty Overview screen :(

agiledigits commented 7 years ago

We have identified the problem and just released v1.1.0. Please try again and let us know what happens.

mlc-mlapis commented 7 years ago

I installed the latest version 1.1.0 (+ several times logout and login) but still having the same problem with "Analysing project ...".

Output views shows a message: Notification handler 'workspace/didChangeConfiguration' failed with message: Cannot read property 'access_token' of undefined.

I do not know if it is important but I work behind a proxy server - its configuration is correct - I have full access to internet from VS Code, npm, ... I have angular-cli installed but the project itself was not created using it.

My angulardoc.json looks:


  "repoId": "7bc64bad-.................................................",
  "directoryFilter": [
    "!typings",
    "!node_modules",
    "!.vscode"
  ],
  "fileFilter": [
    "**/!(*.*spec).ts"
  ],
  "lastSync": 0
}```
agiledigits commented 7 years ago

@mlc-mlapis Please try v1.2.0 and see if it fixed your issues.

mlc-mlapis commented 7 years ago

Thanks. It looks that the problem disappeared now.