Formatting issues after moving widget up/down
See original GitHub issueMight be a dart analyzer problem. I’m not sure.
From here, swapping Padding
up with Container
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Create an advanced widget - Android Developers
This page explains recommended practices for creating a more advanced widget that has a better user experience. Optimizations for updating widget content.
Read more >Add widgets on iPhone - Apple Support
When you see the size you want, tap Add Widget. While the apps are still jiggling, move the widget where you want it...
Read more >Widgets Color Widgets + Icons - Apps on Google Play
From the team behind WatchMaker, the largest watchface design community in the world - get ready to make your home screen unique with...
Read more >Packaged Web Apps (Widgets) - W3C
This specification standardizes a packaging format and metadata for a class of software known commonly as packaged apps or widgets.
Read more >Using the Flutter inspector
Toggle the Select Widget Mode button again to exit widget select mode. When debugging layout issues, the key fields to look at are...
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 FreeTop 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
Top GitHub Comments
Yes, I think this is an issue in Dart Analysis Server. Accidentally I was looking for this assist yesterday and so the same problem.
When you try to
Move widget up
onnew SliverToBoxAdapter
, it gives wrongly formatted code.https://dart-review.googlesource.com/c/sdk/+/39841 should fix this.
I anecdotally confirm too that I haven’t seen this issue happen again. Likely just happening on swaps one level next to widgets with children like @scheglov pointed out.