Document all exported bindings and public methods

[arv]

Right now it seems like I need to add a JSDoc comment for the function/var/method to be documented.

/** Included */
export function f() {}

export function g() {}

I would like to have g be part of my API docs even when there is no JSDoc for it.

Similarly for methods:

class C {
  /** included */
  m() {}
  n() {}
  _o() {}
}

Similarly I would like m and n to be listed as methods of C

Is there an option to do this?

[tmcw]

Hey Erik!

Going to close this ticket in favor of the very similar one posted by Cameron a few days ago: #424

As it stands, documentation.js does require some handwritten documentation in order for things to be included. I think this is the right default, given that it reflects the behavior of other documentation generators and an on-by-default behavior would introduce the potential pitfall of how to not document a specific thing that shouldn't be included.