Open screens/snackbars/dialogs/bottomSheets without context, manage states and inject dependencies easily with Get.

Last update: Jul 2, 2022

Languages: English (this file), Indonesian, Urdu, Chinese, Brazilian Portuguese, Spanish, Russian, Polish, Korean, French.

pub package likes building style: effective dart Discord Shield Get on Slack Telegram Awesome Flutter Buy Me A Coffee

About Get

  • GetX is an extra-light and powerful solution for Flutter. It combines high-performance state management, intelligent dependency injection, and route management quickly and practically.

  • GetX has 3 basic principles. This means that these are the priority for all resources in the library: PRODUCTIVITY, PERFORMANCE AND ORGANIZATION.

    • PERFORMANCE: GetX is focused on performance and minimum consumption of resources. GetX does not use Streams or ChangeNotifier.

    • PRODUCTIVITY: GetX uses an easy and pleasant syntax. No matter what you want to do, there is always an easier way with GetX. It will save hours of development and will provide the maximum performance your application can deliver.

      Generally, the developer should be concerned with removing controllers from memory. With GetX this is not necessary because resources are removed from memory when they are not used by default. If you want to keep it in memory, you must explicitly declare "permanent: true" in your dependency. That way, in addition to saving time, you are less at risk of having unnecessary dependencies on memory. Dependency loading is also lazy by default.

    • ORGANIZATION: GetX allows the total decoupling of the View, presentation logic, business logic, dependency injection, and navigation. You do not need context to navigate between routes, so you are not dependent on the widget tree (visualization) for this. You don't need context to access your controllers/blocs through an inheritedWidget, so you completely decouple your presentation logic and business logic from your visualization layer. You do not need to inject your Controllers/Models/Blocs classes into your widget tree through MultiProviders. For this, GetX uses its own dependency injection feature, decoupling the DI from its view completely.

      With GetX you know where to find each feature of your application, having clean code by default. In addition to making maintenance easy, this makes the sharing of modules something that until then in Flutter was unthinkable, something totally possible. BLoC was a starting point for organizing code in Flutter, it separates business logic from visualization. GetX is a natural evolution of this, not only separating the business logic but the presentation logic. Bonus injection of dependencies and routes are also decoupled, and the data layer is out of it all. You know where everything is, and all of this in an easier way than building a hello world. GetX is the easiest, practical, and scalable way to build high-performance applications with the Flutter SDK. It has a large ecosystem around it that works perfectly together, it's easy for beginners, and it's accurate for experts. It is secure, stable, up-to-date, and offers a huge range of APIs built-in that are not present in the default Flutter SDK.

  • GetX is not bloated. It has a multitude of features that allow you to start programming without worrying about anything, but each of these features are in separate containers and are only started after use. If you only use State Management, only State Management will be compiled. If you only use routes, nothing from the state management will be compiled.

  • GetX has a huge ecosystem, a large community, a large number of collaborators, and will be maintained as long as the Flutter exists. GetX too is capable of running with the same code on Android, iOS, Web, Mac, Linux, Windows, and on your server. It is possible to fully reuse your code made on the frontend on your backend with Get Server.

In addition, the entire development process can be completely automated, both on the server and on the front end with Get CLI.

In addition, to further increase your productivity, we have the extension to VSCode and the extension to Android Studio/Intellij

Installing

Add Get to your pubspec.yaml file:

dependencies:
  get:

Import get in files that it will be used:

import 'package:get/get.dart';

Counter App with GetX

The "counter" project created by default on new project on Flutter has over 100 lines (with comments). To show the power of Get, I will demonstrate how to make a "counter" changing the state with each click, switching between pages and sharing the state between screens, all in an organized way, separating the business logic from the view, in ONLY 26 LINES CODE INCLUDING COMMENTS.

  • Step 1: Add "Get" before your MaterialApp, turning it into GetMaterialApp
void main() => runApp(GetMaterialApp(home: Home()));
  • Note: this does not modify the MaterialApp of the Flutter, GetMaterialApp is not a modified MaterialApp, it is just a pre-configured Widget, which has the default MaterialApp as a child. You can configure this manually, but it is definitely not necessary. GetMaterialApp will create routes, inject them, inject translations, inject everything you need for route navigation. If you use Get only for state management or dependency management, it is not necessary to use GetMaterialApp. GetMaterialApp is necessary for routes, snackbars, internationalization, bottomSheets, dialogs, and high-level apis related to routes and absence of context.

  • Note²: This step is only necessary if you gonna use route management (Get.to(), Get.back() and so on). If you not gonna use it then it is not necessary to do step 1

  • Step 2: Create your business logic class and place all variables, methods and controllers inside it. You can make any variable observable using a simple ".obs".

class Controller extends GetxController{
  var count = 0.obs;
  increment() => count++;
}
  • Step 3: Create your View, use StatelessWidget and save some RAM, with Get you may no longer need to use StatefulWidget.
class Home extends StatelessWidget {

  @override
  Widget build(context) {

    // Instantiate your class using Get.put() to make it available for all "child" routes there.
    final Controller c = Get.put(Controller());

    return Scaffold(
      // Use Obx(()=> to update Text() whenever count is changed.
      appBar: AppBar(title: Obx(() => Text("Clicks: ${c.count}"))),

      // Replace the 8 lines Navigator.push by a simple Get.to(). You don't need context
      body: Center(child: ElevatedButton(
              child: Text("Go to Other"), onPressed: () => Get.to(Other()))),
      floatingActionButton:
          FloatingActionButton(child: Icon(Icons.add), onPressed: c.increment));
  }
}

class Other extends StatelessWidget {
  // You can ask Get to find a Controller that is being used by another page and redirect you to it.
  final Controller c = Get.find();

  @override
  Widget build(context){
     // Access the updated count variable
     return Scaffold(body: Center(child: Text("${c.count}")));
  }
}

Result:

This is a simple project but it already makes clear how powerful Get is. As your project grows, this difference will become more significant.

Get was designed to work with teams, but it makes the job of an individual developer simple.

Improve your deadlines, deliver everything on time without losing performance. Get is not for everyone, but if you identified with that phrase, Get is for you!

The Three pillars

State management

Get has two different state managers: the simple state manager (we'll call it GetBuilder) and the reactive state manager (GetX/Obx)

Reactive State Manager

Reactive programming can alienate many people because it is said to be complicated. GetX turns reactive programming into something quite simple:

  • You won't need to create StreamControllers.
  • You won't need to create a StreamBuilder for each variable
  • You will not need to create a class for each state.
  • You will not need to create a get for an initial value.
  • You will not need to use code generators

Reactive programming with Get is as easy as using setState.

Let's imagine that you have a name variable and want that every time you change it, all widgets that use it are automatically changed.

This is your count variable:

var name = 'Jonatas Borges';

To make it observable, you just need to add ".obs" to the end of it:

var name = 'Jonatas Borges'.obs;

And in the UI, when you want to show that value and update the screen whenever the values changes, simply do this:

Obx(() => Text("${controller.name}"));

That's all. It's that simple.

More details about state management

See an more in-depth explanation of state management here. There you will see more examples and also the difference between the simple state manager and the reactive state manager

You will get a good idea of GetX power.

Route management

If you are going to use routes/snackbars/dialogs/bottomsheets without context, GetX is excellent for you too, just see it:

Add "Get" before your MaterialApp, turning it into GetMaterialApp

GetMaterialApp( // Before: MaterialApp(
  home: MyHome(),
)

Navigate to a new screen:

Get.to(NextScreen());

Navigate to new screen with name. See more details on named routes here

Get.toNamed('/details');

To close snackbars, dialogs, bottomsheets, or anything you would normally close with Navigator.pop(context);

Get.back();

To go to the next screen and no option to go back to the previous screen (for use in SplashScreens, login screens, etc.)

Get.off(NextScreen());

To go to the next screen and cancel all previous routes (useful in shopping carts, polls, and tests)

Get.offAll(NextScreen());

Noticed that you didn't have to use context to do any of these things? That's one of the biggest advantages of using Get route management. With this, you can execute all these methods from within your controller class, without worries.

More details about route management

Get works with named routes and also offers lower-level control over your routes! There is in-depth documentation here

Dependency management

Get has a simple and powerful dependency manager that allows you to retrieve the same class as your Bloc or Controller with just 1 lines of code, no Provider context, no inheritedWidget:

Controller controller = Get.put(Controller()); // Rather Controller controller = Controller();
  • Note: If you are using Get's State Manager, pay more attention to the bindings API, which will make it easier to connect your view to your controller.

Instead of instantiating your class within the class you are using, you are instantiating it within the Get instance, which will make it available throughout your App. So you can use your controller (or class Bloc) normally

Tip: Get dependency management is decoupled from other parts of the package, so if for example, your app is already using a state manager (any one, it doesn't matter), you don't need to rewrite it all, you can use this dependency injection with no problems at all

controller.fetchApi();

Imagine that you have navigated through numerous routes, and you need data that was left behind in your controller, you would need a state manager combined with the Provider or Get_it, correct? Not with Get. You just need to ask Get to "find" for your controller, you don't need any additional dependencies:

Controller controller = Get.find();
//Yes, it looks like Magic, Get will find your controller, and will deliver it to you. You can have 1 million controllers instantiated, Get will always give you the right controller.

And then you will be able to recover your controller data that was obtained back there:

Text(controller.textFromApi);

More details about dependency management

See a more in-depth explanation of dependency management here

Utils

Internationalization

Translations

Translations are kept as a simple key-value dictionary map. To add custom translations, create a class and extend Translations.

import 'package:get/get.dart';

class Messages extends Translations {
  @override
  Map<String, Map<String, String>> get keys => {
        'en_US': {
          'hello': 'Hello World',
        },
        'de_DE': {
          'hello': 'Hallo Welt',
        }
      };
}

Using translations

Just append .tr to the specified key and it will be translated, using the current value of Get.locale and Get.fallbackLocale.

Text('title'.tr);

Using translation with singular and plural

var products = [];
Text('singularKey'.trPlural('pluralKey', products.length, Args));

Using translation with parameters

import 'package:get/get.dart';


Map<String, Map<String, String>> get keys => {
    'en_US': {
        'logged_in': 'logged in as @name with email @email',
    },
    'es_ES': {
       'logged_in': 'iniciado sesión como @name con e-mail @email',
    }
};

Text('logged_in'.trParams({
  'name': 'Jhon',
  'email': '[email protected]'
  }));

Locales

Pass parameters to GetMaterialApp to define the locale and translations.

return GetMaterialApp(
    translations: Messages(), // your translations
    locale: Locale('en', 'US'), // translations will be displayed in that locale
    fallbackLocale: Locale('en', 'UK'), // specify the fallback locale in case an invalid locale is selected.
);

Change locale

Call Get.updateLocale(locale) to update the locale. Translations then automatically use the new locale.

var locale = Locale('en', 'US');
Get.updateLocale(locale);

System locale

To read the system locale, you could use Get.deviceLocale.

return GetMaterialApp(
    locale: Get.deviceLocale,
);

Change Theme

Please do not use any higher level widget than GetMaterialApp in order to update it. This can trigger duplicate keys. A lot of people are used to the prehistoric approach of creating a "ThemeProvider" widget just to change the theme of your app, and this is definitely NOT necessary with GetX™.

You can create your custom theme and simply add it within Get.changeTheme without any boilerplate for that:

Get.changeTheme(ThemeData.light());

If you want to create something like a button that changes the Theme in onTap, you can combine two GetX™ APIs for that:

  • The api that checks if the dark Theme is being used.
  • And the Theme Change API, you can just put this within an onPressed:
Get.changeTheme(Get.isDarkMode? ThemeData.light(): ThemeData.dark());

When .darkmode is activated, it will switch to the light theme, and when the light theme becomes active, it will change to dark theme.

GetConnect

GetConnect is an easy way to communicate from your back to your front with http or websockets

Default configuration

You can simply extend GetConnect and use the GET/POST/PUT/DELETE/SOCKET methods to communicate with your Rest API or websockets.

class UserProvider extends GetConnect {
  // Get request
  Future<Response> getUser(int id) => get('http://youapi/users/$id');
  // Post request
  Future<Response> postUser(Map data) => post('http://youapi/users', body: data);
  // Post request with File
  Future<Response<CasesModel>> postCases(List<int> image) {
    final form = FormData({
      'file': MultipartFile(image, filename: 'avatar.png'),
      'otherFile': MultipartFile(image, filename: 'cover.png'),
    });
    return post('http://youapi/users/upload', form);
  }

  GetSocket userMessages() {
    return socket('https://yourapi/users/socket');
  }
}

Custom configuration

GetConnect is highly customizable You can define base Url, as answer modifiers, as Requests modifiers, define an authenticator, and even the number of attempts in which it will try to authenticate itself, in addition to giving the possibility to define a standard decoder that will transform all your requests into your Models without any additional configuration.

class HomeProvider extends GetConnect {
  @override
  void onInit() {
    // All request will pass to jsonEncode so CasesModel.fromJson()
    httpClient.defaultDecoder = CasesModel.fromJson;
    httpClient.baseUrl = 'https://api.covid19api.com';
    // baseUrl = 'https://api.covid19api.com'; // It define baseUrl to
    // Http and websockets if used with no [httpClient] instance

    // It's will attach 'apikey' property on header from all requests
    httpClient.addRequestModifier((request) {
      request.headers['apikey'] = '12345678';
      return request;
    });

    // Even if the server sends data from the country "Brazil",
    // it will never be displayed to users, because you remove
    // that data from the response, even before the response is delivered
    httpClient.addResponseModifier<CasesModel>((request, response) {
      CasesModel model = response.body;
      if (model.countries.contains('Brazil')) {
        model.countries.remove('Brazilll');
      }
    });

    httpClient.addAuthenticator((request) async {
      final response = await get("http://yourapi/token");
      final token = response.body['token'];
      // Set the header
      request.headers['Authorization'] = "$token";
      return request;
    });

    //Autenticator will be called 3 times if HttpStatus is
    //HttpStatus.unauthorized
    httpClient.maxAuthRetries = 3;
  }
  }

  @override
  Future<Response<CasesModel>> getCases(String path) => get(path);
}

GetPage Middleware

The GetPage has now new property that takes a list of GetMiddleWare and run them in the specific order.

Note: When GetPage has a Middlewares, all the children of this page will have the same middlewares automatically.

Priority

The Order of the Middlewares to run can pe set by the priority in the GetMiddleware.

final middlewares = [
  GetMiddleware(priority: 2),
  GetMiddleware(priority: 5),
  GetMiddleware(priority: 4),
  GetMiddleware(priority: -8),
];

those middlewares will be run in this order -8 => 2 => 4 => 5

Redirect

This function will be called when the page of the called route is being searched for. It takes RouteSettings as a result to redirect to. Or give it null and there will be no redirecting.

GetPage redirect( ) {
  final authService = Get.find<AuthService>();
  return authService.authed.value ? null : RouteSettings(name: '/login')
}

onPageCalled

This function will be called when this Page is called before anything created you can use it to change something about the page or give it new page

GetPage onPageCalled(GetPage page) {
  final authService = Get.find<AuthService>();
  return page.copyWith(title: 'Welcome ${authService.UserName}');
}

OnBindingsStart

This function will be called right before the Bindings are initialize. Here you can change Bindings for this page.

List<Bindings> onBindingsStart(List<Bindings> bindings) {
  final authService = Get.find<AuthService>();
  if (authService.isAdmin) {
    bindings.add(AdminBinding());
  }
  return bindings;
}

OnPageBuildStart

This function will be called right after the Bindings are initialize. Here you can do something after that you created the bindings and before creating the page widget.

GetPageBuilder onPageBuildStart(GetPageBuilder page) {
  print('bindings are ready');
  return page;
}

OnPageBuilt

This function will be called right after the GetPage.page function is called and will give you the result of the function. and take the widget that will be showed.

OnPageDispose

This function will be called right after disposing all the related objects (Controllers, views, ...) of the page.

Other Advanced APIs

// give the current args from currentScreen
Get.arguments

// give name of previous route
Get.previousRoute

// give the raw route to access for example, rawRoute.isFirst()
Get.rawRoute

// give access to Routing API from GetObserver
Get.routing

// check if snackbar is open
Get.isSnackbarOpen

// check if dialog is open
Get.isDialogOpen

// check if bottomsheet is open
Get.isBottomSheetOpen

// remove one route.
Get.removeRoute()

// back repeatedly until the predicate returns true.
Get.until()

// go to next route and remove all the previous routes until the predicate returns true.
Get.offUntil()

// go to next named route and remove all the previous routes until the predicate returns true.
Get.offNamedUntil()

//Check in what platform the app is running
GetPlatform.isAndroid
GetPlatform.isIOS
GetPlatform.isMacOS
GetPlatform.isWindows
GetPlatform.isLinux
GetPlatform.isFuchsia

//Check the device type
GetPlatform.isMobile
GetPlatform.isDesktop
//All platforms are supported independently in web!
//You can tell if you are running inside a browser
//on Windows, iOS, OSX, Android, etc.
GetPlatform.isWeb


// Equivalent to : MediaQuery.of(context).size.height,
// but immutable.
Get.height
Get.width

// Gives the current context of the Navigator.
Get.context

// Gives the context of the snackbar/dialog/bottomsheet in the foreground, anywhere in your code.
Get.contextOverlay

// Note: the following methods are extensions on context. Since you
// have access to context in any place of your UI, you can use it anywhere in the UI code

// If you need a changeable height/width (like Desktop or browser windows that can be scaled) you will need to use context.
context.width
context.height

// Gives you the power to define half the screen, a third of it and so on.
// Useful for responsive applications.
// param dividedBy (double) optional - default: 1
// param reducedBy (double) optional - default: 0
context.heightTransformer()
context.widthTransformer()

/// Similar to MediaQuery.of(context).size
context.mediaQuerySize()

/// Similar to MediaQuery.of(context).padding
context.mediaQueryPadding()

/// Similar to MediaQuery.of(context).viewPadding
context.mediaQueryViewPadding()

/// Similar to MediaQuery.of(context).viewInsets;
context.mediaQueryViewInsets()

/// Similar to MediaQuery.of(context).orientation;
context.orientation()

/// Check if device is on landscape mode
context.isLandscape()

/// Check if device is on portrait mode
context.isPortrait()

/// Similar to MediaQuery.of(context).devicePixelRatio;
context.devicePixelRatio()

/// Similar to MediaQuery.of(context).textScaleFactor;
context.textScaleFactor()

/// Get the shortestSide from screen
context.mediaQueryShortestSide()

/// True if width be larger than 800
context.showNavbar()

/// True if the shortestSide is smaller than 600p
context.isPhone()

/// True if the shortestSide is largest than 600p
context.isSmallTablet()

/// True if the shortestSide is largest than 720p
context.isLargeTablet()

/// True if the current device is Tablet
context.isTablet()

/// Returns a value<T> according to the screen size
/// can give value for:
/// watch: if the shortestSide is smaller than 300
/// mobile: if the shortestSide is smaller than 600
/// tablet: if the shortestSide is smaller than 1200
/// desktop: if width is largest than 1200
context.responsiveValue<T>()

Optional Global Settings and Manual configurations

GetMaterialApp configures everything for you, but if you want to configure Get manually.

MaterialApp(
  navigatorKey: Get.key,
  navigatorObservers: [GetObserver()],
);

You will also be able to use your own Middleware within GetObserver, this will not influence anything.

MaterialApp(
  navigatorKey: Get.key,
  navigatorObservers: [
    GetObserver(MiddleWare.observer) // Here
  ],
);

You can create Global Settings for Get. Just add Get.config to your code before pushing any route. Or do it directly in your GetMaterialApp

GetMaterialApp(
  enableLog: true,
  defaultTransition: Transition.fade,
  opaqueRoute: Get.isOpaqueRouteDefault,
  popGesture: Get.isPopGestureEnable,
  transitionDuration: Get.defaultDurationTransition,
  defaultGlobalState: Get.defaultGlobalState,
);

Get.config(
  enableLog = true,
  defaultPopGesture = true,
  defaultTransition = Transitions.cupertino
)

You can optionally redirect all the logging messages from Get. If you want to use your own, favourite logging package, and want to capture the logs there:

GetMaterialApp(
  enableLog: true,
  logWriterCallback: localLogWriter,
);

void localLogWriter(String text, {bool isError = false}) {
  // pass the message to your favourite logging package here
  // please note that even if enableLog: false log messages will be pushed in this callback
  // you get check the flag if you want through GetConfig.isLogEnable
}

Local State Widgets

These Widgets allows you to manage a single value, and keep the state ephemeral and locally. We have flavours for Reactive and Simple. For instance, you might use them to toggle obscureText in a TextField, maybe create a custom Expandable Panel, or maybe modify the current index in BottomNavigationBar while changing the content of the body in a Scaffold.

ValueBuilder

A simplification of StatefulWidget that works with a .setState callback that takes the updated value.

ValueBuilder<bool>(
  initialValue: false,
  builder: (value, updateFn) => Switch(
    value: value,
    onChanged: updateFn, // same signature! you could use ( newValue ) => updateFn( newValue )
  ),
  // if you need to call something outside the builder method.
  onUpdate: (value) => print("Value updated: $value"),
  onDispose: () => print("Widget unmounted"),
),

ObxValue

Similar to ValueBuilder, but this is the Reactive version, you pass a Rx instance (remember the magical .obs?) and updates automatically... isn't it awesome?

ObxValue((data) => Switch(
        value: data.value,
        onChanged: data, // Rx has a _callable_ function! You could use (flag) => data.value = flag,
    ),
    false.obs,
),

Useful tips

.observables (also known as Rx Types) have a wide variety of internal methods and operators.

Is very common to believe that a property with .obs IS the actual value... but make no mistake! We avoid the Type declaration of the variable, because Dart's compiler is smart enough, and the code looks cleaner, but:

var message = 'Hello world'.obs;
print( 'Message "$message" has Type ${message.runtimeType}');

Even if message prints the actual String value, the Type is RxString!

So, you can't do message.substring( 0, 4 ). You have to access the real value inside the observable: The most "used way" is .value, but, did you know that you can also use...

final name = 'GetX'.obs;
// only "updates" the stream, if the value is different from the current one.
name.value = 'Hey';

// All Rx properties are "callable" and returns the new value.
// but this approach does not accepts `null`, the UI will not rebuild.
name('Hello');

// is like a getter, prints 'Hello'.
name() ;

/// numbers:

final count = 0.obs;

// You can use all non mutable operations from num primitives!
count + 1;

// Watch out! this is only valid if `count` is not final, but var
count += 1;

// You can also compare against values:
count > 2;

/// booleans:

final flag = false.obs;

// switches the value between true/false
flag.toggle();


/// all types:

// Sets the `value` to null.
flag.nil();

// All toString(), toJson() operations are passed down to the `value`
print( count ); // calls `toString()` inside  for RxInt

final abc = [0,1,2].obs;
// Converts the value to a json Array, prints RxList
// Json is supported by all Rx types!
print('json: ${jsonEncode(abc)}, type: ${abc.runtimeType}');

// RxMap, RxList and RxSet are special Rx types, that extends their native types.
// but you can work with a List as a regular list, although is reactive!
abc.add(12); // pushes 12 to the list, and UPDATES the stream.
abc[3]; // like Lists, reads the index 3.


// equality works with the Rx and the value, but hashCode is always taken from the value
final number = 12.obs;
print( number == 12 ); // prints > true

/// Custom Rx Models:

// toJson(), toString() are deferred to the child, so you can implement override on them, and print() the observable directly.

class User {
    String name, last;
    int age;
    User({this.name, this.last, this.age});

    @override
    String toString() => '$name $last, $age years old';
}

final user = User(name: 'John', last: 'Doe', age: 33).obs;

// `user` is "reactive", but the properties inside ARE NOT!
// So, if we change some variable inside of it...
user.value.name = 'Roi';
// The widget will not rebuild!,
// `Rx` don't have any clue when you change something inside user.
// So, for custom classes, we need to manually "notify" the change.
user.refresh();

// or we can use the `update()` method!
user.update((value){
  value.name='Roi';
});

print( user );

StateMixin

Another way to handle your UI state is use the StateMixin<T> . To implement it, use the with to add the StateMixin<T> to your controller which allows a T model.

class Controller extends GetController with StateMixin<User>{}

The change() method change the State whenever we want. Just pass the data and the status in this way:

change(data, status: RxStatus.success());

RxStatus allow these status:

RxStatus.loading();
RxStatus.success();
RxStatus.empty();
RxStatus.error('message');

To represent it in the UI, use:

class OtherClass extends GetView<Controller> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(

      body: controller.obx(
        (state)=>Text(state.name),
        
        // here you can put your custom loading indicator, but
        // by default would be Center(child:CircularProgressIndicator())
        onLoading: CustomLoadingIndicator(),
        onEmpty: Text('No data found'),

        // here also you can set your own error widget, but by
        // default will be an Center(child:Text(error))
        onError: (error)=>Text(error),
      ),
    );
}

GetView

I love this Widget, is so simple, yet, so useful!

Is a const Stateless Widget that has a getter controller for a registered Controller, that's all.

 class AwesomeController extends GetController {
   final String title = 'My Awesome View';
 }

  // ALWAYS remember to pass the `Type` you used to register your controller!
 class AwesomeView extends GetView<AwesomeController> {
   @override
   Widget build(BuildContext context) {
     return Container(
       padding: EdgeInsets.all(20),
       child: Text(controller.title), // just call `controller.something`
     );
   }
 }

GetResponsiveView

Extend this widget to build responsive view. this widget contains the screen property that have all information about the screen size and type.

How to use it

You have two options to build it.

  • with builder method you return the widget to build.
  • with methods desktop, tablet,phone, watch. the specific method will be built when the screen type matches the method when the screen is [ScreenType.Tablet] the tablet method will be exuded and so on. Note: If you use this method please set the property alwaysUseBuilder to false

With settings property you can set the width limit for the screen types.

example Code to this screen code

GetWidget

Most people have no idea about this Widget, or totally confuse the usage of it. The use case is very rare, but very specific: It caches a Controller. Because of the cache, can't be a const Stateless.

So, when do you need to "cache" a Controller?

If you use, another "not so common" feature of GetX: Get.create().

Get.create(()=>Controller()) will generate a new Controller each time you call Get.find<Controller>(),

That's where GetWidget shines... as you can use it, for example, to keep a list of Todo items. So, if the widget gets "rebuilt", it will keep the same controller instance.

GetxService

This class is like a GetxController, it shares the same lifecycle ( onInit(), onReady(), onClose()). But has no "logic" inside of it. It just notifies GetX Dependency Injection system, that this subclass can not be removed from memory.

So is super useful to keep your "Services" always reachable and active with Get.find(). Like: ApiService, StorageService, CacheService.

Future<void> main() async {
  await initServices(); /// AWAIT SERVICES INITIALIZATION.
  runApp(SomeApp());
}

/// Is a smart move to make your Services intiialize before you run the Flutter app.
/// as you can control the execution flow (maybe you need to load some Theme configuration,
/// apiKey, language defined by the User... so load SettingService before running ApiService.
/// so GetMaterialApp() doesnt have to rebuild, and takes the values directly.
void initServices() async {
  print('starting services ...');
  /// Here is where you put get_storage, hive, shared_pref initialization.
  /// or moor connection, or whatever that's async.
  await Get.putAsync(() => DbService().init());
  await Get.putAsync(SettingsService()).init();
  print('All services started...');
}

class DbService extends GetxService {
  Future<DbService> init() async {
    print('$runtimeType delays 2 sec');
    await 2.delay();
    print('$runtimeType ready!');
    return this;
  }
}

class SettingsService extends GetxService {
  void init() async {
    print('$runtimeType delays 1 sec');
    await 1.delay();
    print('$runtimeType ready!');
  }
}

The only way to actually delete a GetxService, is with Get.reset() which is like a "Hot Reboot" of your app. So remember, if you need absolute persistence of a class instance during the lifetime of your app, use GetxService.

Breaking changes from 2.0

1- Rx types:

Before After
StringX RxString
IntX RxInt
MapX RxMap
ListX RxList
NumX RxNum
DoubleX RxDouble

RxController and GetBuilder now have merged, you no longer need to memorize which controller you want to use, just use GetxController, it will work for simple state management and for reactive as well.

2- NamedRoutes Before:

GetMaterialApp(
  namedRoutes: {
    '/': GetRoute(page: Home()),
  }
)

Now:

GetMaterialApp(
  getPages: [
    GetPage(name: '/', page: () => Home()),
  ]
)

Why this change? Often, it may be necessary to decide which page will be displayed from a parameter, or a login token, the previous approach was inflexible, as it did not allow this. Inserting the page into a function has significantly reduced the RAM consumption, since the routes will not be allocated in memory since the app was started, and it also allowed to do this type of approach:

GetStorage box = GetStorage();

GetMaterialApp(
  getPages: [
    GetPage(name: '/', page:(){
      return box.hasData('token') ? Home() : Login();
    })
  ]
)

Why Getx?

1- Many times after a Flutter update, many of your packages will break. Sometimes compilation errors happen, errors often appear that there are still no answers about, and the developer needs to know where the error came from, track the error, only then try to open an issue in the corresponding repository, and see its problem solved. Get centralizes the main resources for development (State, dependency and route management), allowing you to add a single package to your pubspec, and start working. After a Flutter update, the only thing you need to do is update the Get dependency, and get to work. Get also resolves compatibility issues. How many times a version of a package is not compatible with the version of another, because one uses a dependency in one version, and the other in another version? This is also not a concern using Get, as everything is in the same package and is fully compatible.

2- Flutter is easy, Flutter is incredible, but Flutter still has some boilerplate that may be unwanted for most developers, such as Navigator.of(context).push (context, builder [...]. Get simplifies development. Instead of writing 8 lines of code to just call a route, you can just do it: Get.to(Home()) and you're done, you'll go to the next page. Dynamic web urls are a really painful thing to do with Flutter currently, and that with GetX is stupidly simple. Managing states in Flutter, and managing dependencies is also something that generates a lot of discussion, as there are hundreds of patterns in the pub. But there is nothing as easy as adding a ".obs" at the end of your variable, and place your widget inside an Obx, and that's it, all updates to that variable will be automatically updated on the screen.

3- Ease without worrying about performance. Flutter's performance is already amazing, but imagine that you use a state manager, and a locator to distribute your blocs/stores/controllers/ etc. classes. You will have to manually call the exclusion of that dependency when you don't need it. But have you ever thought of simply using your controller, and when it was no longer being used by anyone, it would simply be deleted from memory? That's what GetX does. With SmartManagement, everything that is not being used is deleted from memory, and you shouldn't have to worry about anything but programming. You will be assured that you are consuming the minimum necessary resources, without even having created a logic for this.

4- Actual decoupling. You may have heard the concept "separate the view from the business logic". This is not a peculiarity of BLoC, MVC, MVVM, and any other standard on the market has this concept. However, this concept can often be mitigated in Flutter due to the use of context. If you need context to find an InheritedWidget, you need it in the view, or pass the context by parameter. I particularly find this solution very ugly, and to work in teams we will always have a dependence on View's business logic. Getx is unorthodox with the standard approach, and while it does not completely ban the use of StatefulWidgets, InitState, etc., it always has a similar approach that can be cleaner. Controllers have life cycles, and when you need to make an APIREST request for example, you don't depend on anything in the view. You can use onInit to initiate the http call, and when the data arrives, the variables will be populated. As GetX is fully reactive (really, and works under streams), once the items are filled, all widgets that use that variable will be automatically updated in the view. This allows people with UI expertise to work only with widgets, and not have to send anything to business logic other than user events (like clicking a button), while people working with business logic will be free to create and test the business logic separately.

This library will always be updated and implementing new features. Feel free to offer PRs and contribute to them.

Community

Community channels

GetX has a highly active and helpful community. If you have questions, or would like any assistance regarding the use of this framework, please join our community channels, your question will be answered more quickly, and it will be the most suitable place. This repository is exclusive for opening issues, and requesting resources, but feel free to be part of GetX Community.

Slack Discord Telegram
Get on Slack Discord Shield Telegram

How to contribute

Want to contribute to the project? We will be proud to highlight you as one of our collaborators. Here are some points where you can contribute and make Get (and Flutter) even better.

  • Helping to translate the readme into other languages.
  • Adding documentation to the readme (a lot of Get's functions haven't been documented yet).
  • Write articles or make videos teaching how to use Get (they will be inserted in the Readme and in the future in our Wiki).
  • Offering PRs for code/tests.
  • Including new functions.

Any contribution is welcome!

Articles and videos

GitHub

https://github.com/jonataslaw/getx
Comments
  • 1. Controller not remove and onClose not fired in v4.1.4

    After update to 4.1.4 , I have noticed a some controllers not fired onClose and event this controller not remove from memory !!

    binding.dart

    import 'package:Project/modules/itemAdd/itemAdd.controller.dart';
    import 'package:get/get.dart';
    
    class ItemAddBinding extends Bindings{
      @override
      void dependencies() {
        Get.lazyPut<ItemAddController>(() => ItemAddController());
      }
    }
    
    

    GetPage

     GetPage(
          name: '/item-add',
          page: () => ItemAddView(),
          binding: ItemAddBinding(),
        ),
    
    

    controller.dart

    
    class ItemAddController extends GetxController {
      // controller
      static ItemAddController get to => Get.find();
    
      @override
      void onInit() {
        getActiveOrDefualtBasket();
        super.onInit();
      }
    
    }
    
    

    View.dart

    class ItemAddView extends GetView<ItemAddController> {
      @override
      Widget build(BuildContext context) {
        return Scaffold( .... View Code ......);
    }
    }
    
    

    console log

    
    [GETX] GOING TO ROUTE /item-add
    [GETX] Instance "ItemAddController" has been created
    [GETX] Instance "ItemAddController" has been initialized
    [GETX] CLOSE TO ROUTE /item-add
    < ! ----- missing close controller --- !>
    [GETX] GOING TO ROUTE /item-add
    < ! ----- missing init controller due to not closed --- !>
    [GETX] CLOSE TO ROUTE /item-add
    
    Reviewed by niypoo at 2021-05-12 20:11
  • 2. About "Complete example of the Flutter counter app in just 11 lines with Get"

    Is your feature request related to a problem? Please describe. I my opinion, this example do not show how good GetX is as a state management. When i saw this code, i wondered: why don't simply make a normal variable and update it normally? I know the counter app is too simple to elaborate, but i think it would be better if you made a controller class and a view class, so it would be more realistic.

    Describe the solution you'd like I would suggest something like this:

    
    void main() => runApp(GetMaterialApp(home: Home()));
    
    class CounterController extends RxController {
      final count = 0.obs;
    }
    
    class Home extends StatelessWidget {
      final CounterController controller = Get.find();
      @override
      Widget build(context) {
        return Scaffold(
        appBar: AppBar(
          title: Text("Get change you life"),
        ),
        floatingActionButton: FloatingActionButton(
          onPressed: () => controller.count.value++,
        ),
        body: Center(
          child: Obx(() => Text(controller.count.string)),
        ),
      );
    }
    
    

    Note: i don't know if the controller class needs to extends RxController, i saw one place in README that extended, and other place that did not (and this example you put the .obs inside the view, which made me even more confused)

    Anyway, this is just a suggestion on style of your documentation, i am revising it and want to make some small improvements, step by step

    Reviewed by Nipodemos at 2020-06-05 02:25
  • 3. Get.arguments is Null

    • Reproduce case
    • arrived fcm notification while app is in foreground / background
    • parse payload then route by Get.toNamed(route, arguments: parsed);
    • Get.arguments is null on target page.

    Would you please fix this ?

    Reviewed by zl910627 at 2020-10-02 13:39
  • 4. Minor improvements with small breaking changes

    This contains some minor improvements and a few breaking changes

    1. Added splash screen example to Nav2 api
    2. Added PageBindings that pass GetPageRoute as a parameter to the dependencies method (see https://github.com/jonataslaw/getx/pull/1722)
    3. Added optional pickPagesForRootNavigator to GetDelegate , will be explained in the documentation https://github.com/jonataslaw/getx/pull/2032
    4. [BREAKING] Fixed ValueBuilder throwing due to incorrect nullability handling
    5. [BREAKING] Fixed inconsistent responsive calculation behavior by introducing more explicit APIs
      • isPhoneOrLess
      • isPhoneOrWider
      • isPhone falls back to isPhoneOrLess (old behavior, non breaking)
      • isSmallTabletOrLess
      • isSmallTabletOrWider
      • isSmallTablet falls back to isSmallTabletOrLess (BREAKING)
      • isLargeTabletOrLess
      • isLargeTabletOrWider
      • isLargeTablet falls back to isLargeTabletOrLess (BREAKING)
      • isDesktopOrLess
      • isDesktopOrWider
      • isDesktop falls back to isDesktopOrLess (BREAKING)
      • Also the comparison now works based on the width not the shortest side, which is the consistent way to build the UI
        • design is built based on the known width breakpoints
        • height is assumed small and scrollable
      • Also changed the tests to the new behavior
    6. [BREAKING] changed GetDelegate api signature to return Future<void> instead of Future<T> , if the user wants to get a value from a route, they should either use services or Get.dialogs, the old API was returning a value from a completer, and it wasn't consistent across browser refreshes, so it's for the best they get removed altogether

    Pre-launch Checklist

    • [ ] I updated/added relevant documentation (doc comments with ///).
    • [ ] I added new tests to check the change I am making or feature I am adding, or @jonataslaw said the PR is test-exempt.
    • [x] All existing and new tests are passing.
    Reviewed by ahmednfwela at 2021-12-28 02:54
  • 5. [Docs] Separating documentation in multiple files, and make main README with less information

    This is a draft, it should not be merged yet.

    Hello @jonataslaw ! I am thinking about this for a few days, but i don't even know if that is a good idea. Since README is getting gigantic and it will be even bigger when everything gets documented, the main readme file is getting bloated with information. It's a lot for one place.

    My proposal is to split documentation in different files, make the main README have just a resumed version of all GetX can do, and link for the more extended documentation.

    Advantages:

    • The first contact of new users with get can be better, improving the amount of people that want to try it out, and making easier for them to do this
    • It is easier to maintain, because, if you make an update in just one thing, you can change just one file
    • more organization in docs

    Disavantages:

    • Since it will not have all features on one file, the user can't simply use CTRL + F and search the term he/she wants to learn more
    • We will have to focus on two documentations: the resumed version and the extended version

    I think it worth it. If you like the idea, can you give me some advice of what to put in the main README? I'm with little creativity hahah

    Reviewed by Nipodemos at 2020-06-27 06:03
  • 6. Change between 3.4.6 and 3.5.0/3.5.1 - All controllers are deleted from memory on app resume

    Describe the bug All controllers are deleted from memory upon app resume

    To Reproduce Steps to reproduce the behavior:

    1. Use version 3.4.6 and all is well
    2. Upgrade to 3.5.0 or 3.5.1 and controllers get removed from memory

    Expected behavior Normal behaviour in my app on 3.4.6 when app was backgrounded and resumed.

    I/flutter (10352): [GETX] AuthController has been initialized
    I/flutter (10352): [GETX] GetMaterialController has been initialized
    I/flutter (10352): [GETX] GOING TO ROUTE /
    I/flutter (10352): [GETX] REPLACE ROUTE /
    I/flutter (10352): [GETX] NEW ROUTE /HomeScreen
    I/flutter (10352): [GETX] HomeScreenController has been initialized
    I/flutter (10352): [GETX] NotificationsController has been initialized
    I/flutter (10352): Running CallController onInit();
    I/flutter (10352): Ran _bindEventListeners();
    I/flutter (10352): [GETX] CallController has been initialized
    

    on 3.5.0 or 3.5.1 this happens when app was backgrounded and resumed.

    I/flutter (32716): Loading isLoggedIn as "true" from device.
    I/flutter (32716): [GETX] AuthController has been initialized
    I/flutter (32716): [GETX] GetMaterialController has been initialized
    I/flutter (32716): [GETX] REPLACE ROUTE /
    I/flutter (32716): [GETX] NEW ROUTE null
    I/flutter (32716): [GETX] REPLACE ROUTE null
    I/flutter (32716): [GETX] NEW ROUTE null
    I/flutter (32716): [GETX] HomeScreenController has been initialized
    I/flutter (32716): [GETX] NotificationsController has been initialized
    I/flutter (32716): Running CallController onInit();
    I/flutter (32716): Ran _bindEventListeners();
    I/flutter (32716): [GETX] CallController has been initialized
    I/flutter (32716): Setting title to: Calls
    I/flutter (32716): Building PageView at position: 0
    I/flutter (32716): [GETX] CallsController instance was created at that time
    I/flutter (32716): [GETX] CallsController has been initialized
    I/flutter (32716): Setting title to: Calls
    I/flutter (32716): Building PageView at position: 0
    I/flutter (32716): [GETX] onClose of HomeScreenController called
    I/flutter (32716): [GETX] HomeScreenController deleted from memory
    I/flutter (32716): [GETX] onClose of NotificationsController called
    I/flutter (32716): [GETX] NotificationsController deleted from memory
    I/flutter (32716): [GETX] onClose of CallController called
    I/flutter (32716): [GETX] CallController deleted from memory
    I/flutter (32716): [GETX] Dio deleted from memory
    I/flutter (32716): [GETX] CallsProvider deleted from memory
    I/flutter (32716): [GETX] CallsRepository deleted from memory
    I/flutter (32716): [GETX] onClose of CallsController called
    I/flutter (32716): [GETX] CallsController deleted from memory
    I/flutter (32716): Caught error: A ScrollPositionWithSingleContext was used after being disposed.
    I/flutter (32716): Once you have called dispose() on a ScrollPositionWithSingleContext, it can no longer be used.
    I/flutter (32716): stackTrace: #0      ChangeNotifier._debugAssertNotDisposed.<anonymous closure> (package:flutter/src/foundation/change_notifier
    

    Flutter Version:

    [✓] Flutter (Channel stable, 1.20.2, on Linux, locale en_GB.UTF-8)
        • Flutter version 1.20.2 at /home/ghenry/development/flutter
        • Framework revision bbfbf1770c (2 weeks ago), 2020-08-13 08:33:09 -0700
        • Engine revision 9d5b21729f
        • Dart version 2.9.1
    
    [✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
        • Android SDK at /home/ghenry/Android/Sdk
        • Platform android-30, build-tools 28.0.3
        • Java binary at: /home/ghenry/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/192.6392135/jre/bin/java
        • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
        • All Android licenses accepted.
    
    [✓] Android Studio (version 3.6)
        • Android Studio at /home/ghenry/.local/share/JetBrains/Toolbox/apps/AndroidStudio/ch-0/192.6392135
        • Flutter plugin version 37.1.1
        • Dart plugin version 183.6270
        • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    
    [✓] VS Code (version 1.47.3)
        • VS Code at /usr/share/code
        • Flutter extension version 3.2.0
    
    [✓] Connected device (1 available)
        • sdk gphone x86 (mobile) • emulator-5556 • android-x86 • Android 11 (API 30) (emulator)
    
    

    Get Version: 3.4.6 working, 3.5.0 and 3.5.1 not.

    Describe on which device you found the bug: Android simulater Pixel 3a API 30, Samsung S10e Android 10, iPhone 8, iPhone SE 2nd11 Pro simulator

    Minimal reproduce code My Entry point is:

                initialBinding: InitialBinding(),
                home: SplashScreen()));
    

    ....

    class InitialBinding implements Bindings {
      @override
      void dependencies() {
        Get.put(UserRepository());
        Get.put(AuthController());
      }
    }
    

    which is actually still just like this:

    https://github.com/jonataslaw/getx/issues/223#issuecomment-642350349

    Thanks.

    Reviewed by ghenry at 2020-08-27 15:05
  • 7. How to pass data from GetView to GetXController?

    I have a bottom sheet. Its extends GetView. At depart point, I use Get.bottomSheet to show a bottom sheet, like this:

    Get.bottomSheet(BottomSheetCustm());
    

    But, inside my bottom sheet I have a parameter, ex: int age; This bottom sheet link to a GetxController. ---> My issue is: How to I pass age to Controller to handle business logic? My English is not good. :(

    Reviewed by pqtrong17 at 2021-03-02 02:02
  • 8. Is it possible to use Get package for apps that use CupertinoApp()?

    GetX package readme says:

    • Step 1: Add "Get" before your MaterialApp, turning it into GetMaterialApp

    void main() => runApp(GetMaterialApp(home: Home()));

    • Note: This step in only necessary if you gonna use route management (Get.to(), Get.back() and so on). If you not gonna use it then it is not necessary to do step 1
      

    I'm creating an app for iOS and therefore I use CupertinoApp() widget instead of MaterialApp(). And I want to use route management as well.

    Is it possible to use Get package for apps that use CupertinoApp() ?

    Reviewed by intraector at 2020-09-12 01:52
  • 9. Unhandled Exception: setState() called after dispose()

    Describe the bug The provided code is a simplified abstraction of a bigger snippet. I have a controller that performs actions on init and updates the view, if I make the GetBuilders global parameter for all views that use the controller false and switch views while one is updating I get:

    E/flutter (23637): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: setState() called after dispose(): _GetBuilderState<TestViewModel>#0b190(lifecycle state: defunct, not mounted)
    E/flutter (23637): This error happens if you call setState() on a State object for a widget that no longer appears in the widget tree (e.g., whose parent widget no longer includes the widget in its build). This error can occur when code calls setState() from a timer or an animation callback.
    E/flutter (23637): The preferred solution is to cancel the timer or stop listening to the animation in the dispose() callback. Another solution is to check the "mounted" property of this object before calling setState() to ensure the object is still in the tree.
    E/flutter (23637): This error might indicate a memory leak if setState() is being called because another object is retaining a reference to this State object after it has been removed from the tree. To avoid memory leaks, consider breaking the reference to this object during dispose().
    E/flutter (23637): #0      State.setState.<anonymous closure> (package:flutter/src/widgets/framework.dart:1197:9)
    E/flutter (23637): #1      State.setState (package:flutter/src/widgets/framework.dart:1232:6)
    E/flutter (23637): #2      GetxController.update.<anonymous closure> (package:get/src/state_manager/simple/get_state.dart:15:25)
    E/flutter (23637): #3      _SetBase.forEach (dart:collection/set.dart:438:30)
    E/flutter (23637): #4      GetxController.update (package:get/src/state_manager/simple/get_state.dart:14:21)
    E/flutter (23637): #5      TestViewModel.loading= (package:get_only_example/core/viewmodels/test_view_model.dart:11:5)
    E/flutter (23637): #6      TestViewModel.onInit (package:get_only_example/core/viewmodels/test_view_model.dart:20:5)
    E/flutter (23637): <asynchronous suspension>
    E/flutter (23637): #7      DisposableInterface.onStart (package:get/src/state_manager/rx/rx_interface.dart:30:5)
    E/flutter (23637): #8      _GetBuilderState.initState (package:get/src/state_manager/simple/get_state.dart:97:19)
    E/flutter (23637): #9      StatefulElement._firstBuild (package:flutter/src/widgets/framework.dart:4640:58)
    E/flutter (23637): #10     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4476:5)
    E/flutter (23637): #11     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3446:14)
    E/flutter (23637): #12     Element.updateChild (package:flutter/src/widgets/framework.dart:3214:18)
    E/flutter (23637): #13     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4527:16)
    E/flutter (23637): #14     Element.rebuild (package:flutter/src/widgets/framework.dart:4218:5)
    E/flutter (23637): #15     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:4481:5)
    E/flutter (23637): #16     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4476:5)
    E/flutter (23637): #17     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3446:14)
    E/flutter (23637): #18     Element.updateChild (package:flutter/src/widgets/framework.dart:3214:18)
    E/flutter (23637): #19     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4527:16)
    E/flutter (23637): #20     Element.rebuild (package:flutter/src/widgets/framework.dart:4218:5)
    E/flutter (23637): #21     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:4481:5)
    E/flutter (23637): #22     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4476:5)
    E/flutter (23637): #23     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3446:14)
    E/flutter (23637): #24     Element.updateChild (package:flutter/src/widgets/framework.dart:3214:18)
    E/flutter (23637): #25     SingleChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:5830:14)
    E/flutter (23637): #26     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3446:14)
    E/flutter (23637): #27     Element.updateChild (package:flutter/src/widgets/framework.dart:3214:18)
    E/flutter (23637): #28     SingleChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:5830:14)
    E/flutter (23637): #29     Element.inflateWidget (package:flutter/src/widgets/framework.dart:3446:14)
    E/flutter (23637): #30     Element.updateChild (package:flutter/src/widgets/framework.dart:3214:18)
    E/flutter (23637): #31     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4527:16)
    E/flutter (23637): #32     Element.rebuild (package:flutter/src/widgets/framework.dart:4218:5)
    E/flutter (23637): #33     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:4481:5)
    E/flutter (23637): #34     ComponentElement.mount (package:flutter/src/widgets/framework.dart:4476:5)
    E/flutter (23637): #35     Element.inflateWidget (package:fl
    

    To Reproduce Steps to reproduce the behavior: Run the provided code snippet.

    Expected behavior Execute without error.

    Flutter Version: 1.17.3

    Get Version: 3.4.1

    Minimal reproduce code

    import 'package:flutter/material.dart';
    import 'package:get/get.dart';
    
    import '../../core/viewmodels/test_view_model.dart';
    
    class TestView extends StatelessWidget {
      @override
      Widget build(BuildContext context) {
        return GetBuilder<TestViewModel>(
          init: TestViewModel(),
          global: false,
          builder: (_) => DefaultTabController(
            length: 2,
            child: Scaffold(
              appBar: AppBar(
                title: Text('This is a test'),
                bottom: TabBar(
                  labelPadding: EdgeInsets.symmetric(vertical: 10),
                  tabs: [
                    Text('Tab 1'),
                    Text('Tab 2'),
                  ],
                ),
              ),
              body: TabBarView(
                children: [
                  _Tab1(),
                  _Tab2(),
                ],
              ),
            ),
          ),
        );
      }
    }
    
    class _Tab2 extends StatelessWidget {
      const _Tab2({
        Key key,
      }) : super(key: key);
    
      @override
      Widget build(BuildContext context) {
        return GetBuilder<TestViewModel>(
          init: TestViewModel(),
          global: false,
          builder: (_) => Center(
            child: _.loading ? CircularProgressIndicator() : Text(_.text),
          ),
        );
      }
    }
    
    class _Tab1 extends StatelessWidget {
      const _Tab1({
        Key key,
      }) : super(key: key);
    
      @override
      Widget build(BuildContext context) {
        return GetBuilder<TestViewModel>(
          init: TestViewModel(),
          global: false,
          builder: (_) => Center(
            child: _.loading ? CircularProgressIndicator() : Text(_.text),
          ),
        );
      }
    }
    
    import 'package:get/get.dart';
    
    class TestViewModel extends GetxController {
      String text = '';
      bool _loading = false;
    
      bool get loading => _loading;
    
      set loading(bool value) {
        _loading = value;
        update();
      }
    
      @override
      Future<void> onInit() async {
        super.onInit();
        loading = true;
        await Future.delayed(Duration(seconds: 2));
        text = 'hello';
        loading = false;
      }
    }
    
    Reviewed by Prn-Ice at 2020-07-29 17:07
  • 10. I need your opinion.

    I'm working on version 3.0 of Get, and I need your opinion on some topics.

    1. I have received countless issues and messages asking to change the lib name, as "Get" is the most common word in English, which makes the search IMPOSSIBLE. I even run into questions on StackOverflow by chance, because it is impossible to find something through research. I thought of "GetX" to not have to create another repository, another package in the pub and etc. I could take advantage of Get, and just name the Package name as GetX. If someone has a better suggestion, speak up, or say if you agree with that.

    2. Get will now become a framework (no longer micro), will have its own CLI, its extensions for VsCode / Intellij, and soon a unique solution that will be launched as soon as it is patented (it will be open source, but the idea needs to be protected). We will add internationalization (translation package), Storage (storage of key / value as sharedPreferences, but synchronous), and a Wrapper for ApiREST / Websockets. Get will start working with abstractions, and anyone will be able to extend GetInterface and create micropackages for Get, including you who are reading. Anything you find useful in your day to day, you can integrate this package. All micropackages will be inserted in the readme, and those that do not add size to the lib, or that have a greater number of downloads will be integrated into the core.

    3. I really need opinions on this: Get is currently doing the AOT compilation division. Even though everything seems to be centralized, if you don't use routes, for example, nothing of routes is compiled in the application, only what was used from Get is actually compiled. However, some things like Storage, will require plugins like "path", which will identify the file folder to write to it. What should I do about it?

    a: Create the get-core with as few dependencies as possible, without storage, internationalization, only with injection of routes, dependencies and status and add these features to Get main.

    b: Create a "get-full" with all features, and leave this package as is.

    c: try to create micropackages based on abstraction, and add them by extensions, and the integration settings must be done manually.

    I appreciate any comments.

    Reviewed by jonataslaw at 2020-06-14 02:22
  • 11. Flutter Beta - Caught error: NoSuchMethodError: The method 'pushNamedAndRemoveUntil' was called on null

    Describe the bug On start up of my app, I get this error

    [GETX] "AuthController" has been initialized
    [GETX] "GetMaterialController" has been initialized
    I/flutter ( 6822): Caught error: NoSuchMethodError: The method 'pushNamedAndRemoveUntil' was called on null.
    I/flutter ( 6822): Receiver: null
    I/flutter ( 6822): Tried calling: pushNamedAndRemoveUntil<dynamic>("/login", Closure: (Route<dynamic>) => bool, arguments: null)
    I/flutter ( 6822): stackTrace: #0      Object.noSuchMethod (dart:core-patch/object_patch.dart:51:5)
    I/flutter ( 6822): #1      GetNavigation.offAllNamed (package:get_navigation/src/extension_navigation.dart:262:36)
    I/flutter ( 6822): #2      AuthController.checkLoggedIn (package:SureVoIPTalk/src/controller/auth.dart:72:11)
    I/flutter ( 6822): #3      ever.<anonymous closure> (package:get_rx/src/rx_workers/rx_workers.dart:47:42)
    I/flutter ( 6822): #4      _rootRunUnary (dart:async/zone.dart:1198:47)
    I/flutter ( 6822): #5      _CustomZone.runUnary (dart:async/zone.dart:1100:19)
    I/flutter ( 6822): #6      _CustomZone.runUnaryGuarded (dart:async/zone.dart:1005:7)
    I/flutter ( 6822): #7      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:357:11)
    I/flutter ( 6822): #8      _DelayedData.perform (dart:async/stream_impl.dart:611:14)
    I/flutter ( 6822): #9      _StreamImplEvents.handleNext (dart:async/stream_impl.dart:730:11)
    I/flutter ( 6822): #10     _PendingEvents.schedule.<anonymous closure> (dart:async/stream_impl.dart:687:7)
    I/flutter ( 6822): #11     _rootRun (dart:async/zone.dart:1182:47)
    I/flutter ( 6822): #12     _CustomZone.run (dart:async/zone.dart:1093:19)
    I/flutter ( 6822): #13     _CustomZone.runGuarded (dart:async/zone.dart:997:7)
    I/flutter ( 6822): #14     _Custo
    I/flutter ( 6822): In dev mode. Not sending report to Sentry.io.
    [GETX] GOING TO ROUTE /login
    [GETX] REMOVING ROUTE /
    

    Expected behavior No error

    Flutter Version: [✓] Flutter (Channel beta, 1.22.0-12.1.pre, on Linux, locale en_GB.UTF-8)

    [✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3) [✓] Chrome - develop for the web [✓] Android Studio (version 3.6) [✓] VS Code (version 1.49.0) [✓] Connected device (4 available)

    Getx Version: 3.11.1

    Describe on which device you found the bug: sdk gphone API 30

    Minimal reproduce code

    AuthController

      @override
      void onInit() {
        ever(isLoggedIn, checkLoggedIn);
        _loadLoggedIn();
        _loadUserDetails();
      }
    
      @override
      void onReady() {
        checkLoggedIn(null);
        super.onReady();
      }
    
      void checkLoggedIn(_) {
        if (isLoggedIn.value) {
          Get.offNamed("/home");
        } else {
          Get.offAllNamed("/login");
        }
      }
    

    app.dart:

              home: SplashScreen(),
              getPages: [
                GetPage(
                    name: "/home",
                    page: () => HomeScreen(),
                    binding: HomeBinding()),
                GetPage(name: "/login", page: () => LoginScreen()),
                GetPage(name: "/dialpad", page: () => DialpadScreen())
              ],
            ));
    
    Reviewed by ghenry at 2020-09-23 09:39
  • 12. GetSingleTickerProviderStateMixin ticker always activity,when the page is Invisible!

    ATTENTION: DO NOT USE THIS FIELD TO ASK SUPPORT QUESTIONS. USE THE PLATFORM CHANNELS FOR THIS. THIS SPACE IS DEDICATED ONLY FOR BUGS DESCRIPTION. Fill in the template. Issues that do not respect the model will be closed.

    Describe the bug with GetSingleTickerProviderStateMixin ,the ticker always activity,when the page is Invisible!

    Reproduction code NOTE: THIS IS MANDATORY, IF YOUR ISSUE DOES NOT CONTAIN IT, IT WILL BE CLOSED PRELIMINARY)

    example:

    /// controller
    class YZCookOrderDetailController extends GetxController
        with GetSingleTickerProviderStateMixin {
      var count = 1.obs;
      late Ticker ticker;
    
      @override
      void onInit() {
        super.onInit();
        ticker = this.createTicker((elapsed) {
          print(elapsed);
        });
        ticker.start();
      }
    
      @override
      void onClose() {
        ticker.dispose();
        super.onClose();
      }
    }
    
    /// view
      @override
      Widget build(BuildContext context) {
        return Scaffold(
          backgroundColor: Color(0xFFF8F6F7),
          appBar: AppBar(
            title: Text(
              'detail',
              style:
                  TextStyle(color: Color(YZTheme.colors.color374037), fontSize: 16),
            ),
          ),
          floatingActionButton: FloatingActionButton(onPressed: () {
            Get.to(() => YZCartListPage());
            Future.delayed(Duration(seconds: 2)).then((value) {
              print(controller.ticker);
            });
          }),
          body: Obx(() {
            return Text(controller.count.toString());
          }),
        );
      }
    
    

    To Reproduce Steps to reproduce the behavior:

    1. click floatingActionButton,push to next page
    2. the ticker still isTicking,and the ticker.muted is false

    Expected behavior when push to another page, the ticker isTicking is false,ticker.muted is true

    Screenshots

    Flutter Version: Flutter:2.8.1

    Getx Version: Getx : 4.6.5

    Describe on which device you found the bug: ex: all device

    Minimal reproduce code

    Reviewed by dingjianjaja at 2022-06-23 07:36
  • 13. get 4.6.5.. Get.isDarkMode is always giving false value.

    This code is working fine... Get.changeThemeMode(value ? ThemeMode.dark : ThemeMode.light);

    but it is not updating the ThemeMode value therefore i am always getting false from Get.isDarkMode please correct this issue...

    e.g
    color: Get.isDarkMode ? ColorHelper.darkTertiary : ColorHelper.lightPrimary,
    
    Reviewed by hayatbangash55 at 2022-06-22 10:51
  • 14. Get.changeTheme() shows errors when calling the first time

    Describe the bug When using the Get.changeTheme() function, for the first call I get an error message and the app is showing the home screen. For the second call everything works without errors.

    **Reproduction code

    The function:

    void changeThemeColorTo({@required Color color}) {
      Get.changeTheme(
        Get.theme.copyWith(
            colorScheme: Get.theme.colorScheme.copyWith(primary: color),
            textTheme: Get.textTheme),
      );
    }
    

    The error message I get for the first time I call the function on runtime:

    flutter: ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
    flutter: The following assertion was thrown building AnimatedTheme(duration: 200ms, dirty, state:
    flutter: _AnimatedThemeState#61936(ticker active, ThemeDataTween(ThemeData#f47a3 → ThemeData#257b9))):
    flutter: 'package:flutter/src/painting/text_style.dart': Failed assertion: line 935 pos 12: 'a == null || b
    package:flutter/…/painting/text_style.dart:935
    flutter: == null || a.inherit == b.inherit': is not true.
    flutter:
    flutter: Either the assertion indicates an error in the framework itself, or we should provide substantially
    flutter: more information in this error message to help you determine and fix the underlying cause.
    flutter: In either case, please report this assertion by filing a bug on GitHub:
    flutter:   https://github.com/flutter/flutter/issues/new?template=BUG.md
    flutter:
    flutter: The relevant error-causing widget was:
    flutter:   GetMaterialApp
    

    My GetMaterialApp looks like that:

    GetMaterialApp(
      localizationsDelegates: [
        GlobalMaterialLocalizations.delegate,
        GlobalWidgetsLocalizations.delegate,
        GlobalCupertinoLocalizations.delegate,
        DefaultCupertinoLocalizations.delegate
      ],
      supportedLocales: [
        const Locale('en'),
        const Locale('de'),
        const Locale('es'),
        const Locale('fr'),
        const Locale('it')
      ],
      debugShowCheckedModeBanner: false,
      defaultTransition: Transition.fade,
      theme: ThemeData(
        brightness: Brightness.light,
        splashColor: Colors.transparent,
        highlightColor: Colors.transparent,
        buttonTheme: ButtonThemeData(
          buttonColor: Color.fromRGBO(243, 156, 18, 1),
          padding: EdgeInsets.all(15),
          shape: RoundedRectangleBorder(
            borderRadius: BorderRadius.circular(18.0),
          ),
          splashColor: Colors.transparent,
          textTheme: ButtonTextTheme.primary,
        ),
        colorScheme: ColorScheme(
            primary: _getThemeColor(),
            primaryVariant: Color.fromRGBO(200, 200, 0, 1),
            secondary: Colors.blue,
            secondaryVariant: Colors.blueAccent,
            surface: Colors.white,
            background: Colors.white,
            error: Colors.red,
            onPrimary: Colors.white,
            onSecondary: Colors.white,
            onSurface: Colors.black,
            onBackground: Colors.black,
            onError: Colors.white,
            brightness: Brightness.light),
        textTheme: TextTheme(
          headline1: TextStyle(
              fontSize: 25, color: Colors.black, fontWeight: FontWeight.bold),
          headline3: TextStyle(
              fontSize: 25, color: Colors.black, fontWeight: FontWeight.bold),
          headline4: TextStyle(
              fontSize: 17, color: Colors.black, fontWeight: FontWeight.bold),
          bodyText1: TextStyle(
              fontSize: 16,
              color: Colors.black,
              fontWeight: FontWeight.normal,
              height: 1.3),
          bodyText2: TextStyle(
              fontSize: 14, color: Colors.black, fontWeight: FontWeight.normal),
        ),
      ),
      themeMode: ThemeMode.light,
      title: "....",
      initialRoute: "/",
      initialBinding: InitialBinding(),
      getPages: [
        GetPage(
            name: "/",
            page: () {
              bool isNewUser = checkIfIsNewUser();
    
              if (isNewUser == true) {
                return CupertinoScaffold(
                  body: HomePage(),
                );
              } else {
                return CupertinoScaffold(
                  body: UserHomepage(),
                );
              }
            }),
        GetPage(name: "userHomepage", page: () => UserHomepage()),
      ],
    );
    

    Flutter Version: 1.22.6

    Getx Version: 3.26.0

    Describe on which device you found the bug: iPhone 12 – Real device

    Reviewed by Asored-D at 2022-06-21 13:37
  • 15. Fixed bug in dependency deletion.

    Before the Binding creates dependencies for a new route, the dependencies from the old route are marked as "dirty". However, if the new route adds one of those same dependencies, then the dirty dependency is moved to the 'lateRemove' property and the root dependency is no longer marked 'isDirty'. This means, when Get.delete() is eventually called on the dependency, the lifecycle 'delete()' is called on the new dependency instead of the old one, and the old dependency ends up being removed from memory (To summarize: The delete() method is called on the wrong controller if both the old and new route have the same controller in their Binding.).

    It seems like the delete() lifecycle method should always be called on the same dependency that ends up being removed from memory, which this change fixes.

    Every PR must update the corresponding documentation in the code, and also the readme in english with the following changes.

    Pre-launch Checklist

    • [ ] I updated/added relevant documentation (doc comments with ///).
    • [ ] I added new tests to check the change I am making or feature I am adding, or @jonataslaw said the PR is test-exempt.
    • [ ] All existing and new tests are passing.
    Reviewed by MaximumCookie at 2022-06-20 21:34

Related

Functional programming in Dart and Flutter. All the main functional programming types and patterns fully documented, tested, and with examples.

Fpdart Functional programming in Dart and Flutter. All the main functional programming types and patterns fully documented, tested, and with examples.

Jun 24, 2022
Megaflixz is a movie app for the movie lover in you. Includes all new and upcoming movies and TV series. Also has an option to save movies to watch later list
Megaflixz is a movie app for the movie lover in you. Includes all new and upcoming movies and TV series. Also has an option to save movies to watch later list

MegaflixZ MegaflixZ is a movie app for the movie lover in you. It is an app that displays new and upcoming movies and tv series. Team members Deepak M

Aug 23, 2021
MobX for the Dart language. Hassle-free, reactive state-management for your Dart and Flutter apps.
MobX for the Dart language. Hassle-free, reactive state-management for your Dart and Flutter apps.

Language: English | Português | Chinese mobx.dart MobX for the Dart language. Supercharge the state-management in your Dart apps with Transparent Func

Jun 22, 2022
A simple way to access state while robust and testable.
A simple way to access state while robust and testable.

A state-management library that: catches programming errors at compile time rather than at runtime removes nesting for listening/combining objects ens

Jun 29, 2022
App to Watch Animes And Read Manga.
App to Watch Animes And Read Manga.

App To Watch Anime And Read Manga NOTE: Manga Section Contains 18+ content. Sometimes App may take some time to load. Constants Folder is removed from

Sep 12, 2021
Open screens/snackbars/dialogs/bottomSheets without context, manage states and inject dependencies easily with Get.
Open screens/snackbars/dialogs/bottomSheets without context, manage states and inject dependencies easily with Get.

Open screens/snackbars/dialogs/bottomSheets without context, manage states and inject dependencies easily with Get.

Jun 30, 2022
Open screens/snackbars/dialogs/bottomSheets without context, manage states and inject dependencies easily with Get.
Open screens/snackbars/dialogs/bottomSheets without context, manage states and inject dependencies easily with Get.

Languages: English (this file), Indonesian, Urdu, Chinese, Brazilian Portuguese, Spanish, Russian, Polish, Korean, French. About Get Installing Counte

Jul 2, 2022
A flutter package to display a country, states, and cities. In addition it gives the possibility to select a list of countries, States and Cities depends on Selected, also you can search country, state, and city all around the world.
A flutter package to display a country, states, and cities. In addition it gives the possibility to select a list of countries, States and Cities depends on Selected, also you can search country, state, and city all around the world.

A flutter package to display a country, states, and cities. In addition it gives the possibility to select a list of countries, States and Cities depends on Selected, also you can search country, state, and city all around the world.

Jul 1, 2022
Easy nav - A simple wrapper around flutter navigator, dialogs and snackbar to do those things without context

EasyNav Just a simple wrapper around flutter navigator, dialogs and snackbar to

Feb 26, 2022
Flutter-context-menus - A flutter package to show context menus on right-click or long-press

context_menus A package to show context menus on right-click or long-press. ?? I

Jan 18, 2022
✨A clean and lightweight loading/toast widget for Flutter, easy to use without context, support iOS、Android and Web
✨A clean and lightweight loading/toast widget for Flutter, easy to use without context, support iOS、Android and Web

Flutter EasyLoading English | 简体中文 Live Preview ?? https://nslog11.github.io/flutter_easyloading Installing Add this to your package's pubspec.yaml fi

Jun 22, 2022
FlutterNavigator is a dart library for dealing with the Navigator API without a build context

FlutterNavigator is a dart library for dealing with the Navigator API without a build context. This package wraps the NavigatorKey and provides a cleaner service for navigating without context in your flutter application.

Jun 21, 2022
Navigation the Multiple Screens ( All categories and Favourites Screens ) and add settings to sort the meals based on categories

meals_app Navigation the Multiple Screens ( All categories and Favourites Screens ) and add settings to sort the meals based on categories Getting Sta

Nov 29, 2021
A light weight library to easily manage a progress dialog with simple steps whenever you need to do it. You can easily show and hide it.
A light weight library to easily manage a progress dialog with simple steps whenever you need to do it. You can easily show and hide it.

progress_dialog A light weight package to show progress dialog. As it is a stateful widget, you can change the text shown on the dialog dynamically. T

Jan 21, 2022
A most easily usable cookie management library in Dart. With SweetCookieJar, you can easily manage cookie on your application.
A most easily usable cookie management library in Dart. With SweetCookieJar, you can easily manage cookie on your application.

A most easily usable cookie management library in Dart! 1. About 1.1. Introduction 1.1.1. Install Library 1.1.2. Import It 1.1.3. Use SweetCookieJar 1

May 19, 2022
A most easily usable cache management library in Dart. With CacheStorage, you can easily manage cache on your application.

A most easily usable cache management library in Dart! 1. About 1.1. Introduction 1.1.1. Install Library 1.1.2. Import It 1.1.3. Use CacheStorage 1.2.

Dec 13, 2021
A library that helps you have multiple snackbars as a column

multi_snackbar A set of commands that helps you display more than one snackbar at the same time. Getting Started Make a list of widgets: var widgets =

Dec 23, 2021
A Flutter package to show beautiful animated snackbars directly using overlay
A Flutter package to show beautiful animated snackbars directly using overlay

Easily show beautiful snack bars directly using overlays. Create custom snack bars and show them with awesome animations.

Apr 28, 2022
AuthorizationHeader is an open-sourced Dart library. With AuthorizationHeader, you can easily manage authorization header on your application.

A most easily usable authorization header management library in Dart! 1. About 1.1. Supported 1.1.1. Authorization Header 1.1.2. Authorization Type 1.

Dec 24, 2021
An extension to the bloc state management library which automatically persists and restores bloc states.
An extension to the bloc state management library which automatically persists and restores bloc states.

⚠️ Attention: This repository has been moved to https://github.com/felangel/bloc and is now read-only! An extension to the bloc state management libra

May 20, 2022