Improve single-component usage
See original GitHub issueReact Styleguidist could be awesome for documenting components, like this, but now it’s not.
- New option to disable sidebar.
-
New option,getComponentName()
, to change the title.@visibleName
JSDoc tag — #933 - “Fork me” ribbon with customisable URL.
- New option to hide isolated link (needs discussion).
- Hide path line if it’s empty.
Anything else? Any feedback?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:14 (10 by maintainers)
Top Results From Across the Web
How to Optimize Components to Improve React Performance
In this tutorial, you will learn how to maximize React performance by measuring rendering bottlenecks and optimizing your components.
Read more >Use Component Composition to Improve the Reusability of ...
The key to the above syntax and the ability to seamlessly compose a bigger component using smaller, individual components is React's Context. The...
Read more >Improve Performance With Lazy Components | Angular In Depth
The performance of applications is critical for success. Delaying and avoiding workload will help you. Learn how to achieve that easily with modern...
Read more >5 Ways to Optimize Your Functional React Components
This can be extended to many different use-cases; for example, you can return a JSX component instead of a single value, meaning you...
Read more >Components are Pure Overhead - DEV Community
But when was the last time you wrote an app in a single component? ... To improve initial render performance with a library...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@glebez The general idea is to be able to show anything instead of an actual component name in the style guide UI. I think #868 could be the first step, and the we’ll need to split
displayName
into two properties: actual component name, and name visible in the UI. So probably we don’t need a separate option for that, but we’ll still need to do some refactoring.Hey, I wanna try to go on with this issue. Can you explain a little more on the “New option, getComponentName(), to change the title.” part? What is the general idea behind it? Or if that has already been discussed somewhere, be so kind to point me in that direction. Thanks!