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
Dart 3 introduced new class modifiers, and the examples in the bloc naming conventions make use of the sealed and final class modifiers. The event and state classes generated by the bloc plugin for IntelliJ IDEA deviate from the official documentation by not using these new class modifiers.
Desired Solution
Offer the option to have the bloc plugin for IntelliJ IDEA generate events and states for Dart 3 using the sealed and final class modifiers.
The text was updated successfully, but these errors were encountered:
Apologies for my comment below. I've realized that the registration procedure differs in that it doesn't simply select one option above all sealed event classes. Therefore, please disregard my earlier comment as it was incorrect. Though, I think the exhaustive search can still find its application somewhere within this library.
Are there plans to modify the way handlers are registered in Bloc, particularly in light of the recent updates regarding exhaustive searches on sealed classes? Of course, the current on method works flawlessly. However, I believe integrating the registration process with the basic Dart 3 syntax might be more intuitive and familiar to newcomers to the Bloc library, compared to using a custom method.
Description
Dart 3 introduced new class modifiers, and the examples in the bloc naming conventions make use of the
sealed
andfinal
class modifiers. The event and state classes generated by the bloc plugin for IntelliJ IDEA deviate from the official documentation by not using these new class modifiers.Desired Solution
Offer the option to have the bloc plugin for IntelliJ IDEA generate events and states for Dart 3 using the
sealed
andfinal
class modifiers.The text was updated successfully, but these errors were encountered: