title: What is the proper/canonical formatting of long JSDoc lines?
body: <p>All of the official JSDoc examples have naively simple documentation strings, like the following:</p>
  
  <pre><code>/**
   * @param {string} author - The author of the book.
   */
  </code></pre>
  
  <p>The problem is, in real-life documentation you often have longer documentation strings:</p>
  
  <pre><code>/**
   * @param {string} author - The author of the book, presumably some person who writes well
   */
  </code></pre>
  
  <p>But since most companies (for legitimate readability reasons) have line length limits, the above often isn't acceptable.  However, what I can't figure out is what the "right" way of breaking up those lines should be.</p>
  
  <p>I could do:</p>
  
  <pre><code>/**
   * @param {string} author - The author of the book, presumably some
   * person who writes well
   */
  </code></pre>
  
  <p>But that is difficult to read.  I could instead do:</p>
  
  <pre><code>/**
   * @param {string} author - The author of the book, presumably some
   *                          person who writes well
   */
  </code></pre>
  
  <p>That looks better, but it can result in a ton of lines, especially if the parameter has a long name:</p>
  
  <pre><code>/**
   * @param {string} personWhoIsTheAuthorOfTheBook - The author of the
   *                                                 book, presumably
   *                                                 some person who
   *                                                 writes well
   */
  </code></pre>
  
  <p>So my question is, what is the proper/official/canonical way of formatting  long <code>@param</code> lines (in the code, not in the generated JSDoc) ... or really any long annotation lines for that matter.</p>