CSF: Remove makeDisplayName option

[shilman]

Issue: #7599

What I did

This partially reverts the change made in #7878, keeping the displayName concept, but removing its configurability.

Now we transform the CSF named export using lodash.startCase as the default. If you want other behavior you can use the namedExport.story = { name: 'anything goes' } construct.

    it('should format CSF exports with sensible defaults', () => {
      const testCases = {
        name: 'Name',
        someName: 'Some Name',
        someNAME: 'Some NAME',
        some_custom_NAME: 'Some Custom NAME',
        someName1234: 'Some Name 1234',
        someName1_2_3_4: 'Some Name 1 2 3 4',
      };
      Object.entries(testCases).forEach(([key, val]) => expect(makeDisplayName(key)).toBe(val));
    });

Why I did it

We made hierarchySeparator and hierarchyRootSeparator configurable, and it has been a maintenance nightmare, adding complexity across our codebase and bringing that nightmare to other tools in the Storybook ecosystem.

makeDisplayName is a similar foundational configuration. However since it can contain arbitrary JS code, we expect it will cause an order of magnitude MORE headaches. At the very least we're not ready to sign up for it without a lot more evidence that it's necessary.

How to test

yarn jest --testPathPattern=client_api.test.ts

[vercel]

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.

[ndelangen]

Yeah we should wait adding this configuration until enough requests have come in with actual use cases.

This seems like a smart move to me.

[shilman]

Closing this in favor of #7901 which improves upon this change