Exceeds print-width (test framework describe/it/etc. Needs docs)

Prettier 1.14.2 Playground link

--parser babylon

Input:

describe('View', () => {
  describe('mapDispatchToProps', () => {
    it('Very long text that describes some stuff about stuff about stuff',
      () => {
        assert(
          fakeDispatch.calledWithExactly(getSomethingNiceNowAgain.request({ wazzaaa })),
        );
      });
  });
});

Output:

describe("View", () => {
  describe("mapDispatchToProps", () => {
    it("Very long text that describes some stuff about stuff about stuff", () => {
      assert(
        fakeDispatch.calledWithExactly(
          getSomethingNiceNowAgain.request({ wazzaaa })
        )
      );
    });
  });
});

Expected behavior: The arrow function should be on the line under the string.

[lydell]

The print width is a guideline for Prettier, not a hard limit. Mostly, Prettier stays below it, but there are a few exceptions added by popular demand, such as testing functions and some import statements. There are also some cases where there’s nothing Prettier can do, such as string literals or comments longer than 80 chars. Or if you nest your code 50 levels deep 😃

[oskarer]

Please enlighten me if I’m off, but the 80 characters limit is there for a reason. Doesn’t it destroy the purpose of the whole thing if a line > 80 characters is allowed in some exceptional cases?

I’m mostly referring to fitting several files side by side, where a loose 80 character limit would still force you to side-scroll.