Previewing a component that is scrollable
See original GitHub issueHi!
I have a component that uses the verticalScroll
modifier. Previewing it in AS works fine, but when opening the group which contains this composable in the Showkase activity, I get an exception saying:
java.lang.IllegalStateException: Nesting scrollable in the same direction layouts like ScrollableContainer and LazyColumn is not allowed. If you want to add a header before the list of items please take a look on LazyColumn component which has a DSL api which allows to first add a header via item() function and then the list of items via items().
How should I go about resolving this, or isn’t this functionality taken into account yet?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:14
Top Results From Across the Web
Can you use a scrollable screen in a component?
I am exploring creating a component with functionality of a scrollable screen. I hijacked the canvas from the scrollable screen in app ...
Read more >Scroll View - the Draftbit Docs!
Select the Scroll View component from the Components drawer. You can open the list of components by clicking the + button next to...
Read more >Prototype scrolling with overflow behavior - Figma Help Center
Use this behavior to support scrolling in any direction, like viewing a map ... Select the Instance in the canvas, click Go to...
Read more >Creating a preview for text in a div with an image that's ...
You could add overflow: hidden if you don't want people to see the extra text, or overflow:scroll if you want the extra text...
Read more >Re: System Scroll Bar Appears when Previewing with...
I have this issue too, its super annoying. Im using a Vertical only scroll group.. It doesnt matter how I scale the components...
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
Just pushed a PR that fixes this problem!
I’m going to give it a shot with the latest version of Showkase that’s targeting Compose beta05. Will let you know what I find!