Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Research] Can we get rid of that "No component found" at the bottom there in SB docs panel? #2385

Closed
ssabo1 opened this issue Nov 27, 2019 · 2 comments · Fixed by #2492
Closed
Assignees
Labels
status: PO approved Approved by PO - Ready for Engineer to pick up

Comments

@ssabo1
Copy link
Collaborator

ssabo1 commented Nov 27, 2019

User Story:
As Spark, we want to see if we can get rid of the "No component found" at the bottom there in SB docs panel.

Notes:

  • this was created after testing SB on 11/22

AC:

  • Research if we can get rid of that "No component found" at the bottom there in SB docs panel.
  • If we can, Work with PO to create new Issue.
@ssabo1 ssabo1 added the status: PO approved Approved by PO - Ready for Engineer to pick up label Nov 27, 2019
@ssabo1 ssabo1 added this to the 12.16.19-12.27.19 milestone Nov 27, 2019
@ssabo1 ssabo1 removed this from the 12.16.19-12.27.19 milestone Dec 20, 2019
@ssabo1 ssabo1 added this to the 12.30.19-1.10.20 milestone Dec 27, 2019
@afebbraro
Copy link
Contributor

In researching this, I couldn't replicate the issue anymore. In talking with @yodasw16, I mentioned another issue that I discovered while researching this thats similar to this one. Dave gave me the permission to submit a PR onto storybook to fix it and said to work with @ssabo1 to create an issue for it when she gets back into office. The issue and the details of the problem are here. storybookjs/storybook#9268

@yodasw16
Copy link
Contributor

Is there anything to review here or can this just be closed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: PO approved Approved by PO - Ready for Engineer to pick up
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants