I suggest you ...

Show a 'completeness' score for package documentation

It would be cool to see what percentage of the code is documented. I think this would help users decide if docs are worth reading, and encourage package owners (like me) to improve the docs.

It would be worth having a heuristic to avoid things like this:

+ /// <summary>
+ /// Toes the query string.
+ /// </summary>
+ /// <param name="hash">The hash.</param>
+ /// <returns>Query String</returns>
internal static string ToQueryString(this HashParams hash)

13 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Harry McIntyreHarry McIntyre shared this idea  ·   ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • ZephZeph commented  · 

        Good idea. Even more valuable to me would be knowing the state of the documentation for the API most of the community took a look at, and one step better beyond that would be knowing how the content was rated. So the output would be a report on the API ref most visited and but have poor ratings and a special flag for not documented at all out of that set, or not updated for a given amount of time, say since the last release.

      Feedback and Knowledge Base