http VS riverpod

For example if you want to add TTS functionality to your application, you can use an already existing package for it. If you want to submit POST/GET requests to an API, you can use the http package to add this.

But http package still lacks some features. Recently, the package was updated to 1.0.0. But being able to abort requests is still not supported by the http package. Plus, the package is just a wrapper around the HTTP implementation in dart:io and dart:html

There's also this package which adds the missing cancellation support, an issue open for 2 years.

http

Im using: Flutter with the dart http package;

http: It will be necessary to download the image in the temporary directory.

Add the HTTP package and getx package in pubspec.yaml.

The http package is part of Dart and has everything you need to request any remote server you want, no need to specifically be firebase or supabase. It's a bit low level so you might want to use other packages that make the task of consuming remote services easier.

Step 5:- Integrate the HTTP package from pub.dev in the pubspec.yaml or use the below command

From a library standpoint, I would recommend https://riverpod.dev over any other state management libraries for productivity purposes.

I have the following code. When I hot reload I get an error like this. Apparently this is fixed in dart 3 and Remi mentions a solve here. I am unclear how to refactor my code to achieve the solve without upgrading Flutter to an unstable version (which I've tried and cannot use because of certain render issues).

I saw this official example but it doesn't use riverpod_generator : https://github.com/rrousselGit/riverpod/blob/master/examples/todos/lib/todo.dart

Looking at the riverpod.dev docs, I saw that they were using Docusaurus which led me to creating this site. You can think of it as a guide or your go-to when trying to build gRPC servers and clients using Dart. It's open source hosted at this repo and everyone is really invited to Collaborate.

Riverpod Docs

I think you might need to use a state management if you want to keep the username and email always in scope in your application. Consider using riverpod or provider

You're right, it's Riverpod.

Sources: Riverpod: https://riverpod.dev REST: https://github.com/codeReview-youtube/flutter_auth_api PROJECT: https://github.com/codeReview-youtube/flutter_rest_riverpod_authentication