Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Generated compodoc documentation no longer working - is it still needed?
See original GitHub issueActual Behavior
The generated compodoc is no longer providing the expected documentation for the projects artifacts (components, routing, modules, etc.).
Only the projects Markdown documentation is included for some files.
To generate and test the compodoc documentation run
npm run compodoc:serve
Discussion
We are currently trying to decide whether we should invest time into fixing the compodoc integration or if we should just remove it from this project if nobody is/was using it. The non existing feedback regarding this broken functionality since several releases suggests that nobody is missing this documentation. 😉
Voting 👍 = Keep compodoc and fix it 👎 = Remove compodoc 😕 = I don’t care
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The current status of our documentation can be found here: https://pwa-gh-review-reports.azurewebsites.net/docs/compodoc/index.html
No we have currently no idea why it is no longer working. We have not analyzed this any further yet. We wanted to know if it is even worth to investigate or if nobody is interested in this documentation anyways. If there would be enough interest in a working compodoc documentation we would start to search for the problem. 😉