-
-
Notifications
You must be signed in to change notification settings - Fork 961
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
Android Studio don't shows option to convert StatelessWidget into ConsumerWidget #3769
Comments
Could you make a git project to reproduce the issue? |
@rrousselGit Please take a look on this video https://youtu.be/bLttZ6tOYLQ?si=UMP034zifqkXl946 |
@rrousselGit There is an option to create ConsumerWidget from snippet. There is just no option to create Consumer widget from StatlessWidget. Very little problem and I dont think that its worth your time. Let me know If I can close this issue |
I don't want a video. I want a github repository. I can't run a video :) |
I always manually do this, but this is a great idea and would be very useful for those new to riverpod. |
my device info:
|
The development process has become much slower without the ability to convert widgets |
Try again after adding |
https://raw.githubusercontent.com/rrousselGit/riverpod/master/packages/riverpod_lint/resources/convert_to_consumer_widget.gif
Im using Android Studio Ladybug | 2024.2.1
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.1, on macOS 14.5 23F79 darwin-arm64, locale
en-PL)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] IntelliJ IDEA Community Edition (version 2024.2.3)
[✓] VS Code (version 1.94.0)
[✓] Connected device (6 available)
[✓] Network resources
• No issues found!
Before I was able to convert Flutter widgets into Riverpod widgets but now I cant. If anyone know how to fix this issue please put a comment below.
The text was updated successfully, but these errors were encountered: