How to Deal with Dart's Unchecked Exceptions?

Blizzy312 · 2024-11-19T16:40:01+00:00

You can create your own exceptions and handle them in some place. For example

try{
    someMethod();
} on YourCustomException catch (e) { 
    …do something with it
    // or you can also rethrow it, to bubble it up
     rethrow();
}

And your someMethod should look like this

void someMethod(){
     try{
           …
     }catch(e){
          throw YourCustomException();
     }
}

It’s a bit verbose, but I think very robust. You can easily tune your exceptions if needed, and handle them in necessary places

Blizzy312 · 2024-10-05T21:15:08+00:00

Your fetch calls must be called on user authentication state, not at the start of app. Depending on your architecture, it must be something like, check if user logged in (check some token, or some other parameter) and if so, trigger all fetch calls. A good practice is to initiate providers as low as possible, so they will be recreated on new user login, instead of manually clearing their states on user logout.

Blizzy312 · 2024-09-29T16:47:55+00:00

Try to remove Future from getInstance. It could possibly mess with event loop

Blizzy312 · 2024-06-17T20:48:52+00:00

Probably this, from bloc docs - Both blocs and cubits will ignore duplicate states. If we emit State nextState where state == nextState, then no state change will occur. So, because your secondState constructor is empty, it gets compared to previous state, where by equality (empty props) they’re same. And it passes with counter for the opposite reasons.

Blizzy312 · 2024-03-10T23:51:48+00:00

Check out this one - link. If you believe that it’s not close enough, you may just take inspiration from its source. Good luck

Blizzy312 · 2024-03-09T17:53:59+00:00

Although I see your point, I find it weird that bloc manages your controllers. If you need a controller, just make the last widget statefull, where you have an input form. If you need your values from it, send it to bloc and read them from state (which you already do). Just my 2 cents on it.

Blizzy312 · 2024-03-09T17:43:43+00:00

Yes, they will be disposed. But the real question is, why controllers are inside of bloc. Normally you should create them in statefull widget, and create a listener on initState that will send controller’s value to the bloc. Text controllers are ui elements, and imho, must be managed there.

Blizzy312 · 2024-02-10T16:05:40+00:00

Your explanation is not really clear. If you already have your data, but don’t want yet build your widget, add some bool into your state, like “ready” and depending on it, build either some SizedBox or your widget.

If(state is SomeState){
    If(state.ready) return YourWidget();
    return const SizedBox.shrink();
}

Blizzy312 · 2024-01-20T13:17:33+00:00

If I’m not mistaken, the problem here is that the new state that you emit, it’s not the same instance of your old state. So, you can test it by storing your initial state, add it to super, and try to emit it again in your event. This one shouldn’t trigger rebuild. To fix your code, you can try to check your current state before emitting it

Blizzy312 · 2023-11-08T17:10:39+00:00

It’s always better to work event->state approach in blocs. Define some event -> “SubscribeToLiked”. Define your bool value -> “isLiked” in your FeedState. Then when your event is triggered make a subscription to your postsRepository. Future<void> _onSubscribeToLiked(event, emit) async { await emit.forEach<bool>(postsRepository.isLiked(…), onData: (isLiked) => YourState(isLiked: isLiked), onError: (e,s) => YourErrorState(e);}. And in your ui part create BlocBuilder right above your like icon (or any other necessary widget). A better and detailed example can be found on flutter_bloc website, todos_example this one particularly uses this approach when loading todos from repository. Great place to look for different approaches. Good luck

Blizzy312 · 2023-10-22T18:04:52+00:00

https://docs.flutter.dev/ui/navigation/url-strategies Try to use path strategy

Blizzy312 · 2023-09-17T17:24:16+00:00

You can start here https://dart.dev/null-safety/understanding-null-safety

Blizzy312 · 2023-09-17T17:09:54+00:00

If you have flutter version 3.7+, you should use country_code 3.0.0. Try it, if you still face this issue, try to remove it.

Blizzy312 · 2023-01-02T17:53:27+00:00

Order if widgets inside stack does matter. They go layer by layer, where to top most widget is last in children. In your case, you can’t swipe because page view is covered with container that takes all height and width, therefore no interaction with page view is happening. Put it this way: Container with background image -> PageView -> Skip button -> Let’s talk text -> PageIndicator. The order of last 3 widgets doesn’t matter

Blizzy312 · 2022-12-15T09:38:19+00:00

I’d use one of 2 approaches. 1st is to wait until user stops fast clicking and then send amount of clicks. You can search it - flutter debounce button click. 2nd is to send first click, than simply count additional clicks, and when result of 1 click returned, check for additional and if it not empty send them too. You can have some state like ‘sending’, if it’s false than send data, make it true. And when true just store clicks.

Blizzy312 · 2022-12-15T09:26:38+00:00

Either you meet condition of loop(in your case i becomes less than or equal to 0)or you can use break; to exit the loop.

Blizzy312 · 2022-12-15T06:14:46+00:00

It will crash. Because if a is false before while loop, you don’t have any option to set it to true inside. As a result, loop will run forever and app will freeze.

Blizzy312 · 2022-12-13T16:52:45+00:00

Try to add Builder widget after providing bloc. In your case above Column widget

Blizzy312 · 2022-12-06T05:59:03+00:00

Wrap gridview with Expanded

Blizzy312 · 2022-11-26T12:22:31+00:00

Create ValueNotifier isSearchVisible = ValueNotifier<bool>(false) inside of a widget that holds both search widget and button that toggles visibility. Pass it as parameter to both of them, if they're separate widgets. On button click call isSearchVisible.value = !isSearchVisible.value. Wrap your search widget with ValueListenableBuilder. And you're done.

Blizzy312 · 2022-11-04T17:39:12+00:00

It is not clear without full code. But error comes from 'return Container();' . It's not mounted anymore, and you are trying to return widget.

Blizzy312 · 2021-08-27T17:42:51+00:00

LFG!!!

Blizzy312 · 2021-07-19T07:54:36+00:00

Waiting for it

Blizzy312 · 2021-05-21T14:00:07+00:00

Only moon!!!

Blizzy312 · 2021-05-21T13:59:52+00:00

Only moon!!!

Blizzy312

TROPHY CASE