You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maybe we can even add links to the API docs for these components so developers can find out easily how to add the particular component to their own app?
I have thought about suggesting headers myself. The original intent was to have a dense single screen to show off all the components and how they look in M3. Now that the number and size of the components has grown, perhaps that is unreasonable. Or perhaps we only show the labels when we are on a larger device. @QuncCccccc when you get a chance to add the multi-column layout for larger displays, perhaps you can look at adding header? Also, if we want them to be links we will need to add a dependency to launch them.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
darrenaustin commentedon Sep 20, 2022
I have thought about suggesting headers myself. The original intent was to have a dense single screen to show off all the components and how they look in M3. Now that the number and size of the components has grown, perhaps that is unreasonable. Or perhaps we only show the labels when we are on a larger device. @QuncCccccc when you get a chance to add the multi-column layout for larger displays, perhaps you can look at adding header? Also, if we want them to be links we will need to add a dependency to launch them.
github-actions commentedon Mar 4, 2023
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.