Storybook: addon-info works poorly with nesting & titles

[Lexicality]

Describe the bug
If you use a title or a nested folder in your story name, addon-info shows an ugly title and does not show the documentation for the component

To Reproduce
Create a story with metadata in the title such as Components/ExampleComponent and then look at the story info pane

Expected behavior
The title should not include any metadata and the class documentation should be visible

Screenshots

Code snippets
_example-component.jsx_

import PropTypes from "prop-types";
import React from "react";

/**
 * This is an example component that displays words
 */
export function ExampleComponent({ words }) {
    return <p>{words}</p>;
}

ExampleComponent.propTypes = {
    /** What to show in the component */
    words: PropTypes.string,
};

ExampleComponent.defaultProps = {
    words: "Hello, World!",
};

_example-component.stories.js_

import { storiesOf } from "@storybook/react";
import React from "react";
import { ExampleComponent } from "./example-component";


let storyA = storiesOf("Components|ExampleComponent", module);
storyA.add("Example #1", () => <ExampleComponent />);

let storyB = storiesOf("Components/ExampleComponent", module);
storyB.add("Example #2", () => <ExampleComponent />);

let storyC = storiesOf("ExampleComponent", module);
storyC.add("Example #3", () => <ExampleComponent />);

System:

  System:
    OS: macOS 10.14.6
    CPU: (4) x64 Intel(R) Core(TM) i5-4308U CPU @ 2.80GHz
  Binaries:
    Node: 10.16.0 - /usr/local/bin/node
    Yarn: 1.16.0 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 75.0.3770.142
    Safari: 12.1.2

(ps: I also have Firefox 68.0.1 installed)

Additional context
Story._getComponentDescription checks for a fulltext match against the story title, rather than a partial.

[stale[bot]]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[Lexicality]

I guess I can have a poke at trying to fix this?

[shilman]

@Lexicality absolutely! would welcome a PR for this 🙏

[Lexicality]

I've got a patch that should work but I'm having considerable trouble getting a development environment working for this project

[shilman]

FYI addon-info is being superceded by addon-docs, which fixes a bunch of bugs and is easier to maintain. It’s reached release candidate (RC) status and will be properly released soon. Please give it a try! https://medium.com/storybookjs/storybook-docspage-e185bc3622bf

[Lexicality]

I'm aware, but unfortunately my team's pretty busy right now and I'd vastly prefer to just fix what we're currently using with a patch version update rather than spend any extra time changing things to a new system. 🙂

[shilman]

@Lexicality completely understood. happy to merge the PR and patch it back into 5.1.x once it's ready!

[shilman]

Just saw your dev environment comment. Did you get it working? Happy to help you out on Discord if it's useful: https://discord.gg/UUt2PJb

[stale[bot]]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[stale[bot]]

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!