title: Prettier forces curlyless, single-line if-statement to be on the same line instead for below
body: <p>After reading the <a href="https://eslint.org/docs/rules/" rel="noreferrer">docs for EsLint</a>, I'm using the rule <a href="https://eslint.org/docs/rules/curly" rel="noreferrer"><em>curly</em></a> set to warning for <a href="https://eslint.org/docs/rules/curly#multi-or-nest" rel="noreferrer"><em>multiple or nested</em></a> rows of statements at conditionals.</p>
  <pre><code>&quot;rules&quot;: {
    &quot;curly&quot;:[&quot;warn&quot;, &quot;multi-or-nest&quot;],
    &quot;quotes&quot;:&quot;warn&quot;
  }
  </code></pre>
  <p>It works as expected but when the code is to my satisfaction, Prettier gives me an error suggesting that the statement after the conditional should be put on a single line, which isn't what I want (nor do I want to use the unnecessary curlies).</p>
  <pre><code>// Preferred style
  if(condition)
    doSomething();
  
  if(condition) {
    doSomething();
    doSomethingElse();
  }
  
  // Prettier style
  if(condition) doSomeSome();
  
  if(condition) {
    doSomething();
    doSomethingElse();
  }
  </code></pre>
  <p>I've checked the docs for Prettier but the closest thing to what I look for is <a href="https://prettier.io/docs/en/options.html" rel="noreferrer"><em>bracketSpacing</em></a>, which isn't what I want at all. There's nothing else about multiline bracketting as far I could see.</p>
  <p>How can I make Prettier behave to my liking? (Secondary question: where can I find more info about other rules, except in the official docs?)</p>
  <p>NB. A <a href="https://stackoverflow.com/questions/54326285/prettier-putting-if-statement-on-one-line">somewhat similar question</a> asked a while ago got no answers and the comments suggested the poster to accept the way Prettier wants it to be (i.e. enforcing superfluous curlies). It seems wrong to me that the computer tells me what to like instead of me telling it my an <em>some_rc.json</em> file.</p>
  <p>I also found <a href="https://github.com/prettier/prettier/issues/366" rel="noreferrer">a lengthy discussion</a> proving that there's been a need for such an option since 2017, so I'm inclined to assume that it's been implemented (as I find it hard to believe that the designers simply disregarded the wishes). Am I mistaken?</p>