get

• Allow null body to POST method on GetConnect

• This update attaches two nice features developed by (@SchabanBo): GetPage Children And GetMiddleware In previous versions, to create child pages, you should do something like:

GetPage(
  name: '/home',
  page: () => HomeView(),
  binding: HomeBinding(),
),
GetPage(
  name: '/home/products',
  page: () => ProductsView(),
  binding: ProductsBinding(),
),
GetPage(
  name: '/home/products/electronics',
  page: () => ElectronicsView(),
  binding: ElectronicsBinding(),
),

Although the feature works well, it could be improved in several ways: 1- If you had many pages, the page file could become huge and difficult to read. Besides, it was difficult to know which page was the daughter of which module. 2- It was not possible to delegate the function of naming routes to a subroutine file. With this update, it is possible to create a declarative structure, very similar to the Flutter widget tree for your route, which might look like this:

GetPage(
      name: '/home',
      page: () => HomeView(),
      binding: HomeBinding(),
      children: [
        GetPage(
            name: '/products',
            page: () => ProductsView(),
            binding: ProductsBinding(),
            children: [
              GetPage(
                 name: '/electronics',
                 page: () => ElectronicsView(),
                 binding: ElectronicsBinding(),
              ),
            ],
          ),
      ],
  );

Thus, when accessing the url: '/home/products/electronics' Or use Get.toNamed('/home/products/electronics') it will go directly to the page [ElectronicsView], because the child pages, automatically inherit the name of the ancestral page, so with any small change on any father in the tree all children will be updated. If you change [/products] to [/accessories], you don't nesse update on all child links.

However, the most powerful feature of this version is GetMiddlewares. The GetPage has now new property that takes a list of GetMiddleWare than can perform actions and run them in the specific order.

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.

• Fix wrong reference with unnamed routes and added more tests

• Added GetConnect.

• GetConnect is an easy way to communicate from your back to your front. With it you can:
• Communicate through websockets
• Send messages and events via websockets.
• Listen to messages and events via websockets.
• Make http requests (GET, PUT, POST, DELETE).
• Add request modifiers (like attaching a token to each request made).
• Add answer modifiers (how to change a value field whenever the answer arrives)
• Add an authenticator, if the answer is 401, you can configure the renewal of your JWT, for example, and then it will again make the http request.
• Set the number of attempts for the authenticator
• Define a baseUrl for all requests
• Define a standard encoder for your Model.
• Note1: You will never need to use jsonEncoder. It will always be called automatically with each request. If you define an encoder for your model, it will return the instance of your model class ALREADY FILLED with server data.
• Note2: all requests are safety, you do not need to insert try / catch in requests. It will always return a response. In case of an error code, Response.hasError will return true. The error code will always be returned, unless the error was a connection error, which will be returned Response.hasError, but with error code null.
• These are relatively new features, and also inserted in separate containers. You don't have to use it if you don't want to. As it is relatively new, some functions, such as specific http methods, may be missing.

• Translation to Korean (@rws08)
• Fix Overlays state (@eduardoflorence)
• Update chinese docs (@jonahzheng)
• Added context.isDarkMode to context extensions

• Allow list.assignAll, map.assignAll and set.assignAll operate with null values

• Added GetCupertinoApp
• Added initial suport to navigator 2.0

• Clean RxList, RxMap and RxSet implementation
• Now when declaring an RxList(), it will be started empty. If you want to start a null RxList, you must use RxList(null). Improved GetStream to receive the same parameters as the StreamController, such as onListen, onPause, onResume and onCancel.
• Improve docs

• Fix compilation error on master

• Documentation translated into Russian language. (@Renat Fakhrutdinov, @Doaxan and @BatttA)
• Added error message callback for StateMixin (@eduardoflorence)
• Fix incorrect Get.reference when pop route (@4mb1t)
• Added Uppercase/Capital letter on GetUtils (@AleFachini)
• Redraw the Streams api to use GetStream instead of StreamControllers. Why this change? Dart provides a Streams API that is really rich. However, asynchronous streams add extra latency to ensure that events are delivered in the exact order. It is not yet known whether this latency has any performance impact in mobile applications, and probably not, however, as GetX is also a server-side framework, we need to have the lowest latency at all, since our base is shared. Dart also has a Synchronous Streams api that has very low latency, however, it is not suitable for use in state management for two reasons: 1- Synchronous Streams can only have one listen (see the issue opened by Hixie on dart lang for reference: https://github.com/dart-lang/sdk/issues/22240). This means that we cannot use this api for more than one listener, which is the basis of global state management, where we aim to change the state of more than one location. You can test this with this simple snippet:

void main() {
  var controller = StreamController(sync: true);
  var stream = controller.stream;
  stream.listen((data) {
    print('$data');
    if (data == 'test4') controller.add('test5');
  });

  print('test1');
  controller.add('test2');
  stream.listen((event) {}); // second listen throws a exception
  print('test3');
  controller.add('test4');
  print('test6');
  controller.add('test7');
  print("test8");
}

2- Even with a single listener, the dart's Synchronous Streams api cannot deliver events in the exact order. We plan to work on a PR in the future at dart-lang to address this. So if we remove the line above that causes the exception, we will have the following output in the log:

void main() {
  var controller = StreamController(sync: true);
  var stream = controller.stream;
  stream.listen((data) {
    print('$data');
    if (data == 'test4') controller.add('test5');
  });

  print('test1');
  controller.add('test2');
  // stream.listen((event) {}); // second listen throws a exception
  print('test3');
  controller.add('test4');
  print('test6');
  controller.add('test7');
  print("test8");
}
///////////////////// log:
test1
test2
test3
test4
test6
test8
test5

As we can see, test 4 skips to test 6, which skips to test 8, which skips to test 5. Note that test 7 didn't even appear in the log.

However, if we work with GetStream, everything works as expected:

void main() {
  var controller = GetStream();
  var stream = controller.stream;
  stream.listen((data) {
    print('$data');
    if (data == 'test4') controller.add('test5');
  });

  print('test1');
  controller.add('test2');
  // stream.listen((event) {}); // second listen throws a exception
  print('test3');
  controller.add('test4');
  print('test6');
  controller.add('test7');
  print("test8");
}
///////////////////// log:
test1
test2
test3
test4
test5
test6
test7
test8

The dart documentation is clear that this api should be used with caution, and in view of these tests, we were sure that it is not stable enough to be used as the core of our state management, nor of the websockets notifications and get_server requests.

Clarification about the controversy over benchmarks: In a version prior to changeLog, we talked about the 9000% difference in performance between Streams, and GetStreams that ended up causing a lot of controversy in the community. Initially, we would like to clarify that this does not mean that you will have mobile applications 9000% faster. Only that one of our main resources, showed itself with a high rate of requests, 9000% faster than using traditional streams. In a real world scenario, you will hardly have so many simultaneous requests. Skia renders frames on new devices at up to 120fps. This means that if you have a 10 second animation, you will have 1200 reconstructions. Unless you are working with animations, or something that requires rendering at the skia boundary, you won't need that much power. So this does not mean that we are revolutionizing the mobile world, only that we have created an alternative to Stream Sincronas, which works as expected, and which has satisfactory performance for low latency resources. The benchmarks are real, but that does not mean that you will have mobile applications 9000% faster, but that you have a new feature that performs at this level to use. For reference only, the benchmark can be found (HERE)

In short: asynchronous streams from dart work perfectly, but add a latency that we want to remove on Get_server. Synchronous dart streams have unexpected behaviors, cannot have more than 1 listener and do not deliver events in the correct order, which completely prevents their use in mobile state managements, since you run the risk of displaying data on the wrong screen, since the last event will not always be the last event entered by the sink. The 9000% figures are real, however, they refer to the gross performance between Streams and GetStreams. This does not mean that this number will impact your applications, because you are unlikely to use all of that power.

• Improve Performance: We made modifications to make GetBuilder even faster. We have improved the structure behind it so that listeners are notified faster. Perhaps in version 4.0 everything will be based on this new structure, but maintaining the power and compatibility with streams. If you want to know how much Getx is faster than pure streams or ChangeNotifier (even after the last update using LinkedList), you can create run the repository tests at: (https://github.com/jonataslaw/getx/blob/master/test/benchmarks/benckmark_test.dart)
• Added StateMixin StateMixin allows you to change the state of the controller, and display a loading, an error message, or a widget you want with 0 boilerplate. This makes things like API/Rest communication or websocket absurdly simple, and it's a real revolution in how state management has behaved so far. You no longer need to have a ternary in your code, and you don't need a widget like FutureBuilder, StreamBuilder or even Obx/GetBuilder to encompass your Visibility. This will change with the way you manage the state of your controllers, decrease your boilerplate absurdly, and give you more security in your code.
• Added GetNotifier GetNotifier is a super and powerful ValueNotifier, which in addition to having the life cycle of the controllers, is extremely fast, and can manage a single state, as a simplified immutable state management solution. In theory, the only difference between it and GetxController is the possibility of setting an initial value in the constructor's super (exactly as ValueNotifier does). If the initial value is null, use GetxController. If you need a starting value, GetNotifier can be more useful and have less boilerplate, but both serve the same purpose: to decouple your visualization layer from your presentation logic.
• Other Fixes and improvements:
  • Fixed GetxController is closed twice when smartManagement.full is turn on
  • Fixed phone number validation
  • Fixed some inconsistencies in GetWidget and the life cycle of controllers
  • It made controller testing completely safe with navigation.
  • Improve docs (@eduardoflorence)
  • Improve security types on routes (@unacorbatanegra)
  • Improve code structure with less duplicate code: (@kranfix)
  • Fix named route erroring when route does not exist (@FiercestT)

• Reunification of the package. During the 2 week period, we try to keep this package as a compilation of smaller packages. We were successful in separating, getx is well decoupled and it was only necessary to send the internal folders as packages to pub.dev, however, it became very complicated to contribute to the package. This is because it was necessary to clone the repository, replace all pubspec packages with local paths, and after modification, return the original paths to do the PR. With that, the frequency of updates, which was about 4 to 5 days, became almost 2 weeks, and this is not legal for a community as active as Getx, which uses this package precisely in addition to being modern and performance, be constantly improving. This led contributors to the conclusion that getx works best together. Additional packages will continue to be maintained, and will have the same base as the main package, however, development will take place in the full and main package, and as the addition of new features or bug fixes arrives, we will migrate to the individual packages . Getx reached the mark of 50 contributors today, more than 1500 likes in the pub, and will continue to make development easy.

• Remove spaces whitespaces from dart files

• Fix typos on code and docs (@wbemanuel and @Goddchen)
• Improve: typedef to GetBuilder and Getx widgets
• Improve behaviour of null route on lastest flutter version (@FiercestT)
• Fix onReady called twice on smartManagement.onlyBuilders
• Fix onClose called twice when GetBuilder is used
• Fix default customTransitions, and defaultDuration be ignored on unnamedRoutes
• Transition.native use default Flutter transitions
• Added Get.testMode to use contextless elements on unit tests
• Added Get.appUpdate and improve Get.forceAppUpdate

• Remove spaces whitespaces from dart files

• Added BottomSheet Duration && Export SingleGetTickerProvider (@unacorbatanegra)
• Improve docs from dependencies management (@ngxingyu)
• Fix unknownRoute with null Custom Transition (@marcosfons)
• Optimize capitalize method (@zl910627)
• Added Chinese documentation (@idootop)
• Added TextDirection property on GetMaterialApp to improve RTL layout (@justkawal)
• Remove unnecessary files on git (@nipodemos)
• Fix tags on Get.create() and GetWidget() (@roipeker)
• Update mockito dependency on getTests
• Added GetStatelessWidget, a StatelessWidget base to GetWidget with lifecycle control of controllers. Note: It's a base class, you don't need change to use it or change your GetView, GetWidget StatelessWidget to It.

• Fix docs

• Refactor structure from scratch to split GetX completely into separate packages. When using the main package (get) you will have everything working perfectly together. However, if you only want one of the resources, you can use the packages separately.
• Improve Rx types
• Added RTL support
• Added GetTests, a set of tools to help you create unit tests using Getx
• RAM consumption improved by dividing resources into smaller components, preventing related classes that are unnecessary from being loaded
• Fix example app (missing activity) (@Grohden)
• Added Get.create() lifecycle (@roipeker)
• Added section Contribution videos and articles in Readme (@stefandevo)
• fix isNullOrBlank extension
• Added all operators overload (@grohden)
• Fixes subscription for Rx::bindStream (@roipeker)
• Added Ability to use tags with GetX widgets (@na2axl)
• Change Arguments from Object to dynamic (@roipeker)
• Added Persistent bottomsheet (@mohak852)
• Improve extensions tests (@Nipodemos)
• Refactor Route Observer (@grohden)
• Added print extensions (@unacorbatanegra)
• Update PT-br Readme (@eduardoflorence)
• Fix analyzer crash (@eduardoflorence)
• Fix for switch types usages in GetUtils (@grohden)
• Improvement: RxList, RxSet and RxMap null check in the constructor (@Hitsu91)
• Improve readme example (@dafinoer)

• Fixed the use of tags with lazyPut and added Ability to overwrite "tag" in GetView and GetWidget.

• Fix analyzer

Getx 3.10 released with CLI and Get Server.

• Added: analyser + effective dart (@Grohden)
• Added TextStyle to generalDialog title and message (@roipeker)
• renamed and added defaults transition duration and types in "GetInterface" (@roipeker)
• added missing parameters in Get.to/Get.offAll (@roipeker)
• added optional transitionDuration and transitionCurve to Get.dialog() (@roipeker)
• Changed HashMap<int,GetStateUpdate> to HashSet<GetStateUpdate> and allow update IDs groups on GetBuilder (@roipeker)
• Added a internal VoidCallback in GetStateUpdaterMixin::getUpdate (@roipeker)
• Added Curve property to routes (@roipeker)
• Improve docs, code cleanup, new GetStateUpdaterMixin and GetStateUpdate in favour of StateSetter on GetxController, GetBuilder, SimpleBuilder. (@roipeker)
• Added RxBool.toggle() as an easy shortcut for switching true/false values. (@roipeker)
• Added _RxImp.nil() to easily set the value to null (@roipeker)
• Added missing docs to Rx classes. (@roipeker)
• Added Get.delete(force:false) to Get extensions (@roipeker)
• Added Docs and comments (@nipodemos)
• Added docs to PT-br and fix typos (@eduardoflorence)
• Cleanup route code (@justkawal)
• Extension to facilitate insert widgets inside a CustomScrollView (@alexkharech)
• Fix docs .obs examples (@kai-oswald)
• Added tag capability to GetView
• Improve code separation of RouteManagement and Internacionalization

• Added: Snackbar Status: Open, Opening, Closing and Closed example:

 Get.snackbar('title', 'message', snackbarStatus: (status) {
                  if (status == SnackbarStatus.CLOSED) {
                    // made anything
                  }
                });

• Added: RxSet. Sets can now also be reactive.
• Added isDesktop/isMobile (@roipeker)
• Improve GetPlatform: It is now possible to know which device the user is using if GetPlatform.isWeb is true. context.responsiveValue used device orientation based on web and non-web applications. Now it checks if it is a desktop application (web or desktop application) to do the responsiveness calculation. (@roipeker)
• Change: The documentation previously stated that Iterables should not access the ".value" property. However, many users did not pay attention to this fact, and ended up generating unnecessary issues and bugs in their application. In this version, we focus on code security. Now ".value" is protected, so it cannot be accessed externally by Lists, Maps or Sets.
• Change: Observable lists are now Dart Lists. There is no difference in your use: RxList list = [].obs; And you use List list = [].obs;
• Change: You do not need to access the ".value" property of primitives. For Strings you need interpolation. For num, int, double, you will have the normal operators, and use it as dart types. This way, .value can be used exclusively in ModelClasses. Example:

var name = "Jonny" .obs;
// usage:
Text ("$name");

var count = 0.obs;
// usage:
increment() => count ++;
Text("$count");

Thus: List, Map, Set, num, int, double and String, as of this release, will no longer use the .value property.

NOTE: The changes were not break changes, however, you may have missed the details of the documentation, so if you faced the message: "The member 'value' can only be used within instance members of subclasses of 'rx_list.dart' "you just need to remove the" .value "property from your list, and everything will work as planned. The same goes for Maps and Sets.

• Fix more formatting issues

• Fix formatting issues

• Added RxSet
• Change default logger to developer.log (@jorgegaticav)
• Added BindingsBuilder, ValueBuilder, and ObxValue (@roipeker)
• Fix fallback locale not working if missing country code (@thaihuynhxyz)
• Fix validation of email ".com.br"

• Remove unnecessary whitespaces

• Added logwritter (@stefandevo)
• Added responsiveValue (@juanjoseleca)
• Fixed ghost url for snackbar, bottomsheets, and dialogs and unnamed navigation.

• Fix TextField dispose throw on last Flutter hotfix

• Fix typo on RxList.remove that could cause type errors.
• Remove initialization console print

• Fix exception 'isInit called null' when tags are used in conjunction with dependencies. (@djade007)
• Fix typos (@tiagocpeixoto)

• Fix onInit fired only first time
• Fix language callback(@lundin)
• Fix docs (@nipodemos)

• Fix individual imports

• Structure organization, and improvements.

• Added '[everAll]' Worker: Listen a List of '.obx'
• Added Workers dispose
• Fix transition.noTransition
• Fix TextField and VideoPlayController dispose before transition animation

• Fix extensions (@stefandevo)
• Added CPF to utils options (@kauemurakami)
• Added fenix mode to Get.lazyPut. Use Get.lazyPut<Controller>(()=> Controller(), fenix:true) to have a controller that after being destroyed, has the ability to be recreated in case someone needs it. This is a function that already exists in smartManagement.keepFactory which is now also possible in full mode.
• Fix native transition on android

• Improve transitions and refactor route system

• Prevent black blackground on cupertino fullscreenDialog

• Improve GetBuilder ram usage
• Added method update to Rx Now you no longer need to make an entire class reactive to get an element update from it, you can simply call the update method of its instance, like this:

class User{
  User(this.name = '', this.age = 0);
  String name;
  int age;
}

final user = User().obs;

Obx(()=> Text("Name ${user.value.name}: Age: ${user.value.age}"))

// To update:
user.update((user){
user.name = 'Jonny';
user.age = 18;
});

Now is also possible to access a value without using the ".value". Just open and close parentheses. In the previous example, you could do:

user().name; // before: user.value.name

And it is also possible to set a value without using the value, inserting the value directly into the variable.

user(User('João', 35)); // before: user.value = User('João', 35)

Added fenix mode to Get.lazyPut.

• Update readme banner

• Activate unknownRoute on version 3
• Go back transitions.size and transitions.cupertino

• Expose GetInstance

• Improvement .obs methods

• Added extensions to GetUtils and fix typo on GetUtils.isEmail (@stefandevo)
• Added .gitignore file (@hdeyana)

• Breaking changes on Rx api and GetController and RxController were merged, and now you only have the 'GetxController'
• Refactor routing system. Now you can add custom transitions and more
• Improved the use of dynamic routes, you can now define two different pages according to your arguments.
• Added GetView widget
• Added internacionalization
• Added validations
• Added Get queqe
• Added GetStorage (with separated package)
• Minor bug fixes.

• Added getPages API.
• Deprecated namedPages
• Fix default transition
• Added Duration on Get.offAll(@kluverua)

• Added sort to ListX
• Prepared the framework for version 3

• Added Get.focusScope

• Update readme

• Prevent exceptions on onReady with nullables

• Fix Workers

• Added: onReady on Controllers LifeCycle
• Added: Observable maps
• Refactor: observable variables that now consume even less RAM.