Skip to content
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

Fix: Resolve Java warnings and improve error handling #7977

Closed
wants to merge 1 commit into from

Conversation

jwren
Copy link
Member

@jwren jwren commented Mar 19, 2025

[jules test]

This commit addresses several warnings found in the Java code:

  • Adds a suggestion to update the Bazel workspace configuration when the is missing in .
  • Enhances the error message for emulator listing failures in to include a hint about checking the Android SDK configuration.
  • Increases the number of retry attempts for the Flutter daemon before displaying a warning to the user in , potentially reducing unnecessary notifications for transient issues.
  • Modifies the exception handling in to log the specific exception type and message, aiding in debugging.

These changes aim to improve the robustness and user experience of the Flutter IntelliJ plugin.

This commit addresses several warnings found in the Java code:

- Adds a suggestion to update the Bazel workspace configuration when the  is missing in .
- Enhances the error message for emulator listing failures in  to include a hint about checking the Android SDK configuration.
- Increases the number of retry attempts for the Flutter daemon before displaying a warning to the user in , potentially reducing unnecessary notifications for transient issues.
- Modifies the exception handling in  to log the specific exception type and message, aiding in debugging.

These changes aim to improve the robustness and user experience of the Flutter IntelliJ plugin.
@jwren jwren closed this Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant